Travis issues while searching for lager

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Travis issues while searching for lager

Caragea Silviu
Hello,

Recently my Travis Jobs are failing on linux with :

===> Package not found in any repo: lager 3.6.9
The command "rebar3 compile" exited with 1.
My config is here


Any idea what can cause this ?

Silviu

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: Travis issues while searching for lager

Fred Hebert-2
On 03/23, Caragea Silviu wrote:
>Hello,
>
>Recently my Travis Jobs are failing on linux with :
>
>===> Package not found in any repo: lager 3.6.9
>The command "rebar3 compile" exited with 1.
>

I found https://github.com/silviucpp/erlcass/

The rebar3_hex plugin should be something you install globally, not
something you put in your repo.

The latest rebar3_hex version only works with rebar 3.9.1 and later due
to vendoring issues of core libraries interacting with hex.pm. We had
the first problems with this around January, and finally solved it (with
the help of community contribution) in a way that should be safe later.  
It unfortunately still causes issues when interacting with older rebar3
versions.

You will therefore want to either use an older rebar3_hex version, or a
newer rebar3 version.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: Travis issues while searching for lager

Fred Hebert-2
On 03/25, Caragea Silviu wrote:
>Hello Fred,
>
>Any idea what's be best way to do this in travis config ?
>
>Maybe to add a copy of rebar3 into my repo and run this when compile ?
>

There are two options. To run the newest rebar3 possible, rather than
checking rebar3 into your repository permanently, you can just use the
S3 link for it and do something like

    curl https://s3.amazonaws.com/rebar3/rebar3 && chmod +x rebar3

And then call ./rebar3 in your commands for S3. If you cache the
~/.cache directory, you may want to also call ./rebar3 update.

If the objective is to lock the plugin, you can force-specify a version
for the plugin on your own terms ({project_plugins, [{Plugin, Version}]}
-- here I use project_plugins because it will _not_ be fetched by parent
projects when you put yours as a dependency)


Those are all options that are nicer than checking in (and downloading)
rebar3 for each project that exists.
_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: Travis issues while searching for lager

Caragea Silviu
Awesome, thanks!

Have a nice day,
Silviu

On Mon, Mar 25, 2019 at 7:19 PM Fred Hebert <[hidden email]> wrote:
On 03/25, Caragea Silviu wrote:
>Hello Fred,
>
>Any idea what's be best way to do this in travis config ?
>
>Maybe to add a copy of rebar3 into my repo and run this when compile ?
>

There are two options. To run the newest rebar3 possible, rather than
checking rebar3 into your repository permanently, you can just use the
S3 link for it and do something like

    curl https://s3.amazonaws.com/rebar3/rebar3 && chmod +x rebar3

And then call ./rebar3 in your commands for S3. If you cache the
~/.cache directory, you may want to also call ./rebar3 update.

If the objective is to lock the plugin, you can force-specify a version
for the plugin on your own terms ({project_plugins, [{Plugin, Version}]}
-- here I use project_plugins because it will _not_ be fetched by parent
projects when you put yours as a dependency)


Those are all options that are nicer than checking in (and downloading)
rebar3 for each project that exists.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions