Jenkins incoherence

Lionel Elie Mamane lionel at
Thu Jan 4 08:26:16 UTC 2018

On Thu, Jan 04, 2018 at 08:15:14AM +0100, Markus Mohrhard wrote:
> On Thu, Jan 4, 2018 at 8:06 AM, Lionel Elie Mamane <lionel at> wrote:

>> looks like Jenkins build different code on (Windows and MacOS X) vs
>> GNU/Linux. (...)

>> git checkout -f adf948a0895896976b138fb2e81c8b558c7af68f # timeout=30
>> vs
>> git checkout -f be4f19381ef0ae17c6ef964740fc671258ed0b78 # timeout=30

> Note that we nowadays only build OSX and Windows with jenkins if the linux
> build succeeds. As a result your job did not start a build on these
> platforms and you can notice that if you select the OSX build you'll get
> the results of the 25058 build instead of the 25062.

Indeed. At least in our usage of the tool, it is counter-intuitive
that on the page for 25062, one gets the result and a link to another
build. I assume the Jenkins devs have a reasoning for that. To satisfy
my curiosity, how is that "other build" chosen? Most recent? Most
recent successful?

Now that I look more closely, I also notice that the URL is
constructed the other way round:

 * this build:${BUILD_NUMBER}/Config=${CONFIG}/
 * other build:${CONFIG}/${BUILD_NUMBER}/

Thanks for the explanation, now I will know what to look for :)


More information about the LibreOffice mailing list