AW: Build hangs

[jhm]

After the last Jenkins restart, the jobs run now fine.

Thanks
Jan

> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Dienstag, 10. Juli 2018 09:12
> An: builds@apache.org
> Betreff: AW: Build hangs
> 
> Our nightly job is not working right since 30.06.2018 ...
> https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly
> 
> 
> #9​34   30.06.2018 16:54  @H21   last successful build
>   job config changed
> 2018-07-01_09-22-35
>   by:   SYSTEM
>   what: update plugins: rebuild@1.27->1.28, git@3.7.0->3.9.1,
> analysis-core@1.94->1.95, warnings@4.65->4.88
> 2018-07-01_10-42-28
>   by:   SYSTEM
>   what: change xml-version from 1.0 to 1.1
> #9​36   02.07.2018 11:46  @H23   cancelled, stucks at 'Archiving
> artifacts'
> #9​37   03.07.2018 19:08  @H33   cancelled, stucks at 'Archiving
> artifacts'
> #9​38   04.07.2018 04:57  @H20   cancelled, stucks at 'Archiving
> artifacts'
> #9​39   06.07.2018 17:58  @H32   cancelled, stucks at 'Archiving
> artifacts'
> #9​40   08.07.2018 15:11  @H21   failure, Agent went offline during the
> build
> #9​41   09.07.2018 18:02  @H21   running, stucks at 'Archiving
> artifacts'
> 
> Job #935 is not available any more. I think it's the same as with #936
> and therefore deleted (max 5 failed builds).
> 
> The real work (build, checks) is done right, but after that, the
> "archiving artifacts" doesn't work.
> I don't have access to any system logs, so I can't see any possible
> reason.
> 
> I don't believe, that the job config changes by the system upgrade are
> responsible for that behaviour, because the build itself is working -
> it's just the archiving. But this is the only change I could see.
> 
> 
> Does have anyone an idea?
> 
> 
> cheers
> Jan
> 
> 

AW: Build hangs

[jhm]

Our nightly job is not working right since 30.06.2018 ...
https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly


#9​34   30.06.2018 16:54  @H21   last successful build
  job config changed
2018-07-01_09-22-35 
  by:   SYSTEM
  what: update plugins: rebuild@1.27->1.28, git@3.7.0->3.9.1, 
analysis-core@1.94->1.95, warnings@4.65->4.88
2018-07-01_10-42-28
  by:   SYSTEM
  what: change xml-version from 1.0 to 1.1
#9​36   02.07.2018 11:46  @H23   cancelled, stucks at 'Archiving artifacts'
#9​37   03.07.2018 19:08  @H33   cancelled, stucks at 'Archiving artifacts'
#9​38   04.07.2018 04:57  @H20   cancelled, stucks at 'Archiving artifacts'
#9​39   06.07.2018 17:58  @H32   cancelled, stucks at 'Archiving artifacts'
#9​40   08.07.2018 15:11  @H21   failure, Agent went offline during the build
#9​41   09.07.2018 18:02  @H21   running, stucks at 'Archiving artifacts'

Job #935 is not available any more. I think it's the same as with #936 and 
therefore deleted (max 5 failed builds).

The real work (build, checks) is done right, but after that, the "archiving 
artifacts" doesn't work.
I don't have access to any system logs, so I can't see any possible reason.

I don't believe, that the job config changes by the system upgrade are 
responsible for that behaviour, because 
the build itself is working - it's just the archiving. But this is the only 
change I could see.


Does have anyone an idea?


cheers
Jan

AW: Build hangs

[jhm]

Thanks, works.

Now I have found the note in the docs about permission.
How should we deal with that? A list with names via Jira, via mail to 
builds@ao, one post per person?

cheers
Jan

> -Ursprüngliche Nachricht-
> Von: Gav [mailto:ipv6g...@gmail.com]
> Gesendet: Montag, 2. Juli 2018 10:03
> An: builds
> Betreff: Re: Build hangs
> 
> Ok you should all have Cancel job perms again.
> 
> HTH
> 
> Gav...
> 
> On Mon, Jul 2, 2018 at 8:51 AM, Gav  wrote:
> 
> > Hi,
> >
> > We upgraded the main Jenkins yesterday to 2.121.1.
> >
> > The changelog [1] states:-
> >
> > "...The Job/Build permission no longer implies the Job/Cancel
> permission.
> > The latter needs to be granted explicitly to users who previously got
> > it via this relationship. (issue 14713
> > ) ..."
> >
> > The intention being, able to give build permission to folks without
> > allowing them to cancel.
> >
> > I'll be traveling soon, but hope to take a look at our perms before I
> > go, if not, when I get back.
> >
> > As mentioned yesterday in the upgrade email, I encourage everyone to
> > read the upgrade docs.
> >
> > Thanks
> >
> > Gav...
> >
> > [1] -  https://jenkins.io/changelog-stable/
> >
> >
> > On Mon, Jul 2, 2018 at 6:55 AM, Jan Matèrne (jhm) 
> > wrote:
> >
> >> > > Our nightly build hangs for seven hours [1].
> >> > >
> >> > > Could someone kill that so the next could start?
> >> >
> >> >
> >> >
> >> > Cancelled via the UI. Did you try that? That’s ordinarily self-
> service.
> >> >
> >>
> >> Yes - no 'abort job' for me (jhm).
> >> Neither on the concrete build, nor on the job, nor in the Ant group,
> >> nor on the main page.
> >> At work I could cancel the build via the build queue, but nothing
> here.
> >> Maybe missing rights?
> >>
> >> Jan
> >>
> >>
> >
> >
> > --
> > Gav...
> >
> 
> 
> 
> --
> Gav...

AW: Build hangs

[jhm]

> > Our nightly build hangs for seven hours [1].
> >
> > Could someone kill that so the next could start?
> 
> 
> 
> Cancelled via the UI. Did you try that? That’s ordinarily self-service.
> 

Yes - no 'abort job' for me (jhm).
Neither on the concrete build, nor on the job, nor in the Ant group, nor on the 
main page.
At work I could cancel the build via the build queue, but nothing here.
Maybe missing rights?

Jan