Re: My Jenkins builds fail checking out. Why?

[Andrew Johnson via Core-talk <core-talk at aps.anl.gov>]

    Hi Dirk,

On 2/6/20 1:56 AM, Zimoch Dirk (PSI) via Core-talk wrote:

> For 12 days now my Jenkins build fails for 3.15 checking out the sources:
>
> 19:02:10 Fetching upstream changes from https://git.launchpad.net/epics-base
> 19:02:10  > git fetch --tags --progress https://git.launchpad.net/epics-base +refs/heads/*:refs/remotes/origin/*
> 19:02:10  > git rev-parse origin/3.15^{commit} # timeout=10
> 19:02:10  > git rev-parse 3.15^{commit} # timeout=10
> 19:02:10 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
>
> Builds for 3.14 and 7.0 succeed. 3.16 fails as well.
>
> Can somebody give me a hint what has changed and what I may have to change in my Jenkins configuration?
>     
    Nothing has changed as far as I know, but Launchpad does seem to be
    getting more unreliable. Have you tried wiping out the job's
    workspace to have Jenkins check out the git repo again from scratch?
    You can do that from the job's Workspace page.
    
> I have:
> Repository URL https://git.launchpad.net/epics-base
> Branch Specifier 3.15
>
> For the other versions I have Branch Specifier 3.14, 3.16, and 7.0.
>     
    We plan to never commit anything to the 3.14 or 3.16 branches again.
    I have disabled my jobs for those but haven't deleted them.
    
    @Torsten — the git commands that Jenkins uses are usually generated
    internally by the Jenkins software, we only get to modify them by
    enabling and disabling features in the specific job configuration.
    
    - Andrew
    
-- 
Complexity comes for free, Simplicity you have to work for.