Re: How to create/update Jenkins job via REST API in Java?

2022-04-11 Thread 'Daniel Beck' via Jenkins Users
On Mon, Apr 4, 2022 at 11:13 AM Jon Brohauge wrote: > Whenever I try to POST a job, using a Basic Authentication with the > “username:password” base64 encoded, I get a 403. > Crumbs are session-specific since 2.176.2: https://www.jenkins.io/doc/upgrade-guide/2.176/#upgrading-to-jenkins-lts-2-176

Re: Reasons for workspace cleanup

2022-04-11 Thread Fabian Cenedese
>>Workspaces Jenkins considers "unused" are wiped periodically. While this is >>intended to be safe, i.e., never delete the last workspace, or workspaces of >>running builds, it's not impossible that "active" workspaces are caught in >>rare circumstances. Check the workspace cleanup log in you

Re: Reasons for workspace cleanup

2022-04-11 Thread 'Daniel Beck' via Jenkins Users
On Mon, Apr 11, 2022 at 2:05 PM Fabian Cenedese wrote: > At 13:53 11.04.2022, you wrote: > > >Workspaces Jenkins considers "unused" are wiped periodically. While this > is intended to be safe, i.e., never delete the last workspace, or > workspaces of running builds, it's not impossible that "acti

Re: Reasons for workspace cleanup

2022-04-11 Thread Fabian Cenedese
At 13:53 11.04.2022, you wrote: >Workspaces Jenkins considers "unused" are wiped periodically. While this is >intended to be safe, i.e., never delete the last workspace, or workspaces of >running builds, it's not impossible that "active" workspaces are caught in >rare circumstances. Check the w

Re: Reasons for workspace cleanup

2022-04-11 Thread 'Daniel Beck' via Jenkins Users
Workspaces Jenkins considers "unused" are wiped periodically. While this is intended to be safe, i.e., never delete the last workspace, or workspaces of running builds, it's not impossible that "active" workspaces are caught in rare circumstances. Check the workspace cleanup log in your Jenkins hom