Hi Kenneth, I see behaviour that doesn't quite reflect what you describe.
This is usually my setup: ~/easyconfigs -- git Repo with all easyconfigs. Any successful build will be committed as per our config /apps/prod/easybuild/sources -- configued source path as per the config file If I have a new easyconfig, as well as the sources, placed in ~/easyconfigs eb will simply pick up the sources and proceed. So there's no additional configuration required. Is that a side effect of my usabe (command line is usually "eb --robot ~/easyconfigs myConfig.eb") or intended behaviour to work without additional options. As per "recommended usage": Once the easyconfig works I usually just place the file directly in /apps/proc/easybuild/sources without even taking the subdirectories into consideration and that also works without any additional effort on my side. Best, Martin On Wed, Mar 23, 2016 at 12:24 PM Kenneth Hoste <[email protected]> wrote: > Hi John-Paul, > > > On 23/03/16 12:17, John-Paul Robinson wrote: > > So what's the preferred practice for jdks and similar items that required > manual download? > > It seems that manually placing them in the target directory like > .local/easybuild/sources/j/java is potentially error prone and not > immediately obvious. It would be better to have a way to say "find this > upstream in the cwd of where I'm calling eb, or this explicit path" or > something similar. > > Is there such a direction? > > > Yes, you can specify the source path that EasyBuild should consider on the > 'eb' command line: > > eb --source-path $PWD ... > > (or just use '.' rather than $PWD) > > I guess a command line option to copy a tarball to the source path would > be interesting too, but I'm not sure that's worth the trouble (since you'd > need to both specify the location of the tarball and the software name it's > intended for)... > > > regards, > > Kenneth > > > > ~jpr > > > On 03/23/2016 02:29 AM, Martin wrote: > > To my knowledge Ward is correct. You might search the interwebs for > various solutions to the URL. I usually simply download it but I found the > actual culprit is that easybuild doesn't manage the sources in terms of it > doesn't place them in the sources directory configured if it can find it in > the current directory. > > On Tue, Mar 22, 2016 at 3:47 PM Ward Poelmans <[email protected]> > wrote: > >> On 22-03-16 15:40, John-Paul Robinson wrote: >> > Hi, >> > >> > How are folks dealing with staging jdk downloads for ebs that require >> > them. Given the Oracle process for accessing the jdks require logins, >> > we find it necessary to manually place the jdk file in the >> > .local/easybuild/sources/j/java directory. >> > >> > Is this the reality of downloads that require authn or is there some >> > feature to do this more cleanly? >> >> I thought that it is possible to do it automatically but it's not legal >> to do it? >> >> Ward >> >> -- > -- > http://www.xing.com/profile/Martin_Marcher > http://www.linkedin.com/in/martinmarcher > Mobil: +43 / 660 / 62 45 103 > UID: ATU68801424 > > > > -- -- http://www.xing.com/profile/Martin_Marcher http://www.linkedin.com/in/martinmarcher Mobil: +43 / 660 / 62 45 103 UID: ATU68801424
