Thanks, Ernesto,
That must be it: I don’t have any permission even to see the configuration of these jobs, but I had edit permissions on the gerrit jobs for the Neon branch while I was working on that with Céline.
On 8 April, 2016 at 16:47:30, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Hi Christian.
I see the retrigger option on both jobs. Perhaps it has to do
with your permissions? I don't see any options anywhere to enable
others to see them.
Do you want me to retrigger some jobs?
Hi, Team,
Failed Gerrit builds in Hudson usually (in my experience in the
Papyrus project and, I think, some Gerrit builds in Papyrus-RT)
have a “re-trigger” link in the sidebar, that just kicks off the
build again on the assumption that it will proceed differently
because of a change in environmental factors.
I don’t see
this option in the master branch Gerrit builds:
Consequently, I have a Gerrit review that is -1ed because a build
was aborted (possibly by our infamous noon hour job-killing
gremlin). I can’t just rebase the change to trigger a new
build because Gerrit complains about the merge status, and I would
rather not have to make a “real” change in the code just to
re-trigger the build.
Why don’t
these builds have the re-trigger option? And could someone
please fix them?
Thanks,
Christian
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|