Re: jenkins endpoints

[Mark Waite]

On Monday, July 25, 2022 at 8:14:02 PM UTC-6 maanideep wrote:

> Hi,
>
> could someone please get me Jenkins REST API endpoint for project build .
>
> https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API#ArtifactoryRESTAPI-PROJECTS
> please help
>
> something similar to this
>

See the "REST API" link at the bottom right side of the Jenkins page for 
the job.  There is a link "REST API".  When that link is clicked, it opens 
a page that describes many different portions of the REST API for that job.

For 
example, 
https://ci.jenkins.io/job/Plugins/job/elastic-axis-plugin/job/master/api/ 
will show the REST API for the Elastic Axis plugin job on ci.jenkins.io 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/93811d6a-1c91-4e18-8ba3-d445ecd82131n%40googlegroups.com.

jenkins endpoints

[MANIDEEP R KUMMITHA]

 Hi,

could someone please get me Jenkins REST API endpoint for project build .
https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API#ArtifactoryRESTAPI-PROJECTS
please help

something similar to this

Regards,
manideep

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a4ac4468-8c49-4f05-83e1-cbf184ec0027n%40googlegroups.com.

Enforce appending @ to workspace directory even if concurrent builds run on different nodes

['Dirk Heinrichs' via Jenkins Users]

Hi,

when running concurrent builds of the same job, Jenkins usually adds an 
"@" suffix to the workspace name so that those builds can't interfere 
with each other, but only if the concurrent builds are running on the same 
node. This prevents usage of a shared network filesystem for the workspaces on 
each agent. Is there a way to enforce adding the suffix, even if the builds are 
running on different nodes?

Thanks...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: 
www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a01e8827dfb3aac1937fed8e23759e81bd2d1e83.camel%40opentext.com.

Re: "keep this build forever" via rest api?

[LnT]

Thanks a lot. This works.
*java -jar jenkins-cli.jar keep-build  *

On Friday, July 22, 2022 at 6:52:56 PM UTC+5:30 dheinric wrote:

> Am Freitag, dem 22.07.2022 um 05:00 -0700 schrieb LnT:
>
> I get gone with toggleLogKeep in My old Jenkins ver. 2.190.1 
> 
>  
> Now upgraded to Jenkins 2.332.3 
> 
> Stopped now with *ERROR 403 No valid crumb was included in the request*
> what could be the issue ?
>
>
> If you were using username/pw to access the REST API in your old Jenkins, 
> you might need to switch to username/api-token now. Or, even simpler, 
> switch to the built-in SSH server:
>
> % ssh -p  -i path/to/keyfile user@jenkins-host help keep-build
> java -jar jenkins-cli.jar keep-build NAME BUILD#
> Mark the build to keep the build forever.
>  NAME   : Item name
>  BUILD# : Build number
>
>
> HTH...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18 <+49%202226%201596618>
> *Email*: dhei...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0f6e86f1-0ccd-4988-b13b-32090f48a68bn%40googlegroups.com.