content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
fail as a result. [#testing-library-pull-request-changes] === Testing library pull request changes By adding `@Library('my-shared-library@pull//head') \_` at the top of a library consumer Jenkinsfile, you can test your pipeline library pull request changes \_\_in situ\_\_ if your pipeline library is hosted on GitHub an... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
-0.08343653380870819,
-0.09119823575019836,
0.0066688950173556805,
0.002017081482335925,
0.04889566823840141,
-0.05525185167789459,
-0.08625033497810364,
-0.029352828860282898,
-0.0027969246730208397,
-0.017844321206212044,
-0.011566284112632275,
-0.05111154913902283,
-0.0056365299969911575,... | 0.006765 |
= Branches and Pull Requests In the xref:./jenkinsfile.adoc[previous section] a `Jenkinsfile` which could be checked into source control was implemented. This section covers the concept of \*Multibranch\* Pipelines which build on the `Jenkinsfile` foundation to provide more dynamic and automatic functionality in Jenkin... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/multibranch.adoc | main | jenkins | [
-0.02291139028966427,
-0.11629237234592438,
-0.04752242937684059,
-0.027272839099168777,
-0.01902681775391102,
-0.07375306636095047,
-0.0508178249001503,
-0.0024569835513830185,
0.023785829544067383,
-0.019741535186767578,
-0.07965900003910065,
-0.03485874831676483,
-0.007299648132175207,
... | 0.04403 |
= Pipeline Development Tools Jenkins Pipeline includes xref:./getting-started.adoc#built-in-documentation[built-in documentation] and the xref:./getting-started.adoc#snippet-generator[Snippet Generator] which are key resources when developing Pipelines. They provide detailed help and information that is customized to t... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/development.adoc | main | jenkins | [
-0.06251154839992523,
-0.06088291481137276,
-0.04811985790729523,
-0.019564470276236534,
0.023492464795708656,
-0.08365081250667572,
-0.022537197917699814,
0.010418303310871124,
-0.026252584531903267,
-0.03967325761914253,
-0.04059186577796936,
-0.07309283316135406,
-0.03012894093990326,
-... | 0.047302 |
== Running a Pipeline // TODO: WEBSITE-495 - flesh out placeholder sections. === Multibranch See xref:./multibranch.adoc[the Multibranch documentation] for more information. === Parameters See xref:./jenkinsfile.adoc#handling-parameters[the Jenkinsfile documentation] for more information == Restarting or Rerunning a Pi... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/running-pipelines.adoc | main | jenkins | [
0.01289980486035347,
-0.07183638960123062,
-0.0018146595684811473,
-0.013866987079381943,
-0.04870957136154175,
-0.045953329652547836,
-0.0595865361392498,
-0.025650691241025925,
-0.042648766189813614,
-0.07215864956378937,
-0.049181073904037476,
-0.012801526114344597,
-0.057952068746089935,... | 0.009742 |
// or preserveStashes(buildCount: 5) // <2> } ---- <1> The default number of runs to preserve is 1, just the most recent completed build. <2> If a number for `buildCount` outside of the range of 1 to 50 is specified, the Pipeline will fail with a validation error. When a Pipeline completes, it will check to see if any ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/running-pipelines.adoc | main | jenkins | [
-0.03819803521037102,
0.0023467233404517174,
0.046403463929891586,
0.011030766181647778,
-0.04162757843732834,
-0.05601798743009567,
-0.13142400979995728,
-0.05665148049592972,
-0.011784135363996029,
-0.036896850913763046,
-0.09729453921318054,
-0.003548197913914919,
-0.012370707467198372,
... | 0.001298 |
:page-aliases: user-docs:pipeline:overview.adoc = Getting started with Pipeline As mentioned xref:index.adoc[previously], Jenkins Pipeline is a suite of plugins that supports implementing and integrating continuous delivery pipelines into Jenkins. Pipeline provides an extensible set of tools for modeling simple-to-comp... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
-0.10434038192033768,
-0.0640062764286995,
0.008383022621273994,
-0.01194757129997015,
-0.042400941252708435,
-0.06533748656511307,
-0.010757301934063435,
0.015016715042293072,
0.00965450331568718,
-0.04199722036719322,
-0.07800088822841644,
-0.033699795603752136,
-0.011934025213122368,
0.... | 0.072707 |
It is recommended to avoid using spaces in item names, since doing so may uncover bugs in scripts that do not properly handle spaces in directory paths. . Scroll down and click \*Pipeline\*, then click \*OK\* at the end of the page to open the Pipeline configuration page (whose \*General\* tab is selected). + [.boxshad... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
0.007966045290231705,
-0.02807311899960041,
0.04674050584435463,
0.0619763508439064,
-0.022916968911886215,
-0.016466232016682625,
-0.018965596333146095,
0.005864418111741543,
0.007868749089539051,
0.03903525322675705,
-0.011389574967324734,
-0.036285340785980225,
0.03931356966495514,
-0.0... | -0.051593 |
UI's] \*Script\* text area of the Pipeline configuration page. To make this easier, your Pipeline's `Jenkinsfile` can be written in a text editor or integrated development environment (IDE) and committed to source control footnote:scm[] (optionally with the application code that Jenkins will build). Jenkins can then ch... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
-0.006677505560219288,
-0.040289733558893204,
-0.03202880173921585,
0.004358226433396339,
-0.004216129891574383,
-0.01012501958757639,
-0.03624291345477104,
0.07944311946630478,
-0.032534338533878326,
-0.024867333471775055,
-0.0746263638138771,
-0.07801630347967148,
0.02501416578888893,
-0... | 0.006143 |
reference to "Generate Pipeline Script" button which needs to be renamed in a future release of Pipeline: https://issues.jenkins.io/browse/JENKINS-40550 //// [.boxshadow] image:user-docs:pipeline:snippet-generator.png[alt="Snippet Generator",width=100%] To access additional information and/or documentation about the st... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
-0.03564949333667755,
-0.006792491767555475,
0.049237146973609924,
0.04663781076669693,
0.0038405435625463724,
0.011812728829681873,
-0.04868004471063614,
-0.030457358807325363,
-0.00020094927458558232,
-0.0349898636341095,
-0.08488480001688004,
-0.04950100928544998,
0.01852058619260788,
-... | -0.007835 |
= Pipeline Best Practices This guide provides a small selection of best practices for pipelines and points out the most common mistakes. The goal is to point pipeline authors and maintainers towards patterns that result in better Pipeline execution and away from pitfalls they might otherwise not be aware of. This guide... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.059667330235242844,
-0.004203797318041325,
-0.04803379997611046,
-0.04737969860434532,
-0.06648693233728409,
-0.10964179039001465,
-0.04361449554562569,
0.06053794175386429,
-0.04860725253820419,
-0.019530244171619415,
-0.05776532366871834,
-0.019543569535017014,
-0.05102110281586647,
-... | -0.020291 |
to perform the HTTP request from the agent, for example using a tool like `curl` or `wget`, as appropriate. If the result must be later in the Pipeline, try to filter the result on the agent side as much as possible so that only the minimum required information must be transmitted back to the Jenkins controller. === Re... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.040111854672431946,
0.04253889620304108,
-0.034922558814287186,
0.007410036865621805,
-0.05621848255395889,
-0.08279301971197128,
-0.12184794992208481,
-0.04254457727074623,
0.06397150456905365,
0.01760534942150116,
-0.060631707310676575,
-0.02827398106455803,
0.01701807603240013,
-0.06... | 0.021219 |
the same. Lastly, because of the ubiquitous use of these steps throughout Pipelines, if something is coded incorrectly/inefficiently the results can be catastrophic to Jenkins. === Avoiding large global variable declaration files Having large variable declaration files can require large amounts of memory for little to ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.022980645298957825,
0.02914939634501934,
0.043976686894893646,
0.016959816217422485,
0.003903695149347186,
-0.08424509316682816,
-0.07443556934595108,
-0.008483008481562138,
0.08631150424480438,
0.010662179440259933,
-0.03204827010631561,
0.005030839703977108,
-0.022554239258170128,
-0.... | 0.004116 |
of calculating their value and storing that value in a variable. [#using-noncps] ==== Using `@NonCPS` If necessary, you can use the `@NonCPS` annotation to disable the CPS transformation for a specific method whose body would not execute correctly if it were CPS-transformed. Just be aware that this also means the Groov... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.04538130387663841,
0.05301289260387421,
-0.0893602967262268,
-0.016093537211418152,
-0.05098646879196167,
-0.047190431505441666,
-0.011968410573899746,
0.03775379806756973,
0.0001305356272496283,
-0.037167392671108246,
0.019022569060325623,
-0.06558141857385635,
-0.025824815034866333,
-... | -0.032762 |
= Using Docker with Pipeline Many organizations use link:https://www.docker.com[Docker] to unify their build and test environments across machines, and to provide an efficient mechanism for deploying applications. Starting with Pipeline versions 2.5 and higher, Pipeline has built-in support for interacting with Docker ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.0247249323874712,
-0.002425986574962735,
-0.014316062442958355,
-0.028185537084937096,
-0.006494331173598766,
-0.09245770424604416,
-0.029239945113658905,
0.028385687619447708,
-0.013747172430157661,
-0.037965450435876846,
-0.08057886362075806,
-0.07382873445749283,
0.010341213084757328,
... | 0.029371 |
`~/.m2` between Pipeline runs utilizing the link:https://hub.docker.com/\_/maven/[`maven` container], avoiding the need to re-download dependencies for subsequent Pipeline runs. [pipeline] ---- // Declarative // pipeline { agent { docker { image 'maven:3.9.9-eclipse-temurin-21' args '-v $HOME/.m2:/root/.m2' } } stages ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.019026009365916252,
0.021658560261130333,
-0.000743976270314306,
-0.05855398625135422,
0.05297871679067612,
-0.08055949956178665,
-0.06467676907777786,
-0.0229168888181448,
0.044454820454120636,
-0.051780425012111664,
0.00048819807125255466,
-0.09159690141677856,
-0.0017303647473454475,
... | 0.005498 |
and should include: \* `/usr/local/bin` \* `/usr/bin` \* `/bin` \* `/usr/sbin` \* `/sbin` \* `/Applications/Docker.app/Contents/Resources/bin/` \* `/Users/XXX/Library/Group\ Containers/group.com.docker/Applications/Docker.app/Contents/Resources/bin` (where `XXX` is replaced by your user name) Now, restart jenkins using... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.017884718254208565,
0.056147925555706024,
0.021417487412691116,
0.012534144334495068,
-0.005100272595882416,
-0.060528893023729324,
-0.0388936847448349,
-0.06058703362941742,
-0.022624686360359192,
-0.010861537419259548,
-0.06997920572757721,
-0.03984946757555008,
0.009721201844513416,
... | 0.000401 |
the current directory by default. This can be overridden by providing a directory path containing a `Dockerfile` as the second argument of the `build()` method, for example: [source,groovy] ---- node { checkout scm def testImage = docker.build("test-image", "./dockerfiles/test") // <1> testImage.inside { sh 'make test'... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.011111867614090443,
0.02357400394976139,
-0.05733520910143852,
0.027189020067453384,
0.09254299104213715,
-0.03799360617995262,
0.032647937536239624,
0.03108711913228035,
-0.037708550691604614,
-0.0050377026200294495,
-0.008609235286712646,
-0.040599334985017776,
0.0442325659096241,
0.0... | -0.059477 |
= Using a Jenkinsfile This section builds on the information covered in xref:pipeline:getting-started.adoc[Getting started with Pipeline] and introduces more useful steps, common patterns, and demonstrates some non-trivial `Jenkinsfile` examples. Creating a `Jenkinsfile`, which is checked into source control footnote:s... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.07231995463371277,
-0.05859522521495819,
-0.07170524448156357,
0.015794949606060982,
0.02502988837659359,
-0.10042790323495865,
0.00236507598310709,
0.02175714075565338,
-0.03348919749259949,
0.0029051778838038445,
-0.01355237141251564,
-0.04051739722490311,
-0.016443708911538124,
-0.05... | 0.124532 |
viewed as a glue layer to bind the multiple phases of a project's development lifecycle (build, test, deploy, etc) together. Jenkins has a number of plugins for invoking practically any build tool in general use, but this example will simply invoke `make` from a shell step (`sh`). The `sh` step assumes the system is Un... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.09141018241643906,
0.06368344277143478,
0.029757602140307426,
-0.0048362016677856445,
0.013965887948870659,
-0.05351267009973526,
-0.08787994086742401,
-0.06310337036848068,
0.05477297306060791,
0.016484761610627174,
-0.025409933179616928,
-0.049547187983989716,
0.03788303956389427,
-0.... | 0.091331 |
{ stage('Deploy') { when { expression { currentBuild.result == null || currentBuild.result == 'SUCCESS' // <1> } } steps { sh 'make publish' } } } } // Script // node { /\* .. snip .. \*/ stage('Deploy') { if (currentBuild.result == null || currentBuild.result == 'SUCCESS') { // <1> sh 'make publish' } } /\* .. snip ..... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
0.0006704682600684464,
0.07348068058490753,
0.019489198923110962,
0.03618790954351425,
0.050505850464105606,
-0.06732115894556046,
-0.07085291296243668,
-0.0020351966377347708,
-0.040750205516815186,
0.009336954914033413,
-0.03373097628355026,
-0.09321995079517365,
0.028904570266604424,
-0... | 0.00094 |
{ /\* .. snip .. \*/ withEnv(["PATH+MAVEN=${tool 'M3'}/bin"]) { sh 'mvn -B verify' } } ---- <1> An `environment` directive used in the top-level `pipeline` block will apply to all steps within the Pipeline. <2> An `environment` directive defined within a `stage` will only apply the given environment variables to steps ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.03068680129945278,
0.03745981678366661,
-0.00934516079723835,
0.02949429303407669,
0.017723647877573967,
-0.03668801113963127,
-0.0487377904355526,
-0.023935982957482338,
-0.02388721890747547,
0.014435268007218838,
-0.0658886581659317,
-0.0856323391199112,
0.036584265530109406,
0.002221... | -0.008149 |
capturing the credential value by other means. A Pipeline that uses credentials can also disclose those credentials. Don't allow untrusted Pipeline jobs to use trusted credentials. <2> In this Pipeline example, the credentials assigned to the two `AWS\_...` environment variables are scoped globally for the entire Pipel... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.022663436830043793,
0.016003474593162537,
-0.051279738545417786,
-0.02480389177799225,
-0.02536642923951149,
-0.016185898333787918,
0.021304253488779068,
0.01956017315387726,
0.04199691861867905,
-0.01018993929028511,
-0.07108689844608307,
-0.10887026786804199,
0.08740106970071793,
0.00... | -0.048713 |
example, the credentials assigned to the three `BITBUCKET\_COMMON\_CREDS...` environment variables are scoped only to `Example stage 1`, so these credential variables are not available for use in this `Example stage 2` stage's steps. If, however, the `environment` directive in this Pipeline were moved immediately withi... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.05081089213490486,
-0.009635109454393387,
-0.011642271652817726,
-0.04664935544133186,
-0.016748541966080666,
-0.02273998223245144,
0.02309473045170307,
0.051715072244405746,
0.01643374003469944,
-0.005534466356039047,
-0.01521107368171215,
-0.09596934169530869,
0.05209119990468025,
-0.... | -0.058601 |
name of the environment variable that will be bound to the unique alias associated with the certificate. \*\* \*Credentials\* - choose the certificate credentials stored in Jenkins. The value of this field is the credential ID, which Jenkins writes out to the generated snippet. \* \*Docker client certificate\* - to han... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.018626809120178223,
0.056091152131557465,
-0.008009528741240501,
-0.009518945589661598,
-0.031366512179374695,
-0.04422116279602051,
0.015327892266213894,
0.02857062593102455,
0.059595003724098206,
-0.03714460879564285,
-0.11800329387187958,
-0.14959123730659485,
0.12608060240745544,
0.... | -0.088029 |
the \*Sample Step\* field's \*withCredentials: Bind credentials to variables\* option in the \*Snippet Generator\*, only credentials which your current Pipeline project/item has access to can be selected from any \*Credentials\* field's list. While you can manually write a `withCredentials( ... ) { ... }` step for your... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.08207715302705765,
0.016421454027295113,
-0.06578132510185242,
-0.02531370334327221,
-0.07331176847219467,
-0.010403561405837536,
0.06166473403573036,
0.10392183065414429,
-0.022839954122900963,
0.0017336384626105428,
-0.06279110163450241,
-0.09296650439500809,
0.08041401207447052,
-0.0... | -0.056429 |
This is because the sensitive environment variable will be interpolated during Groovy evaluation, and the environment variable's value could be made available earlier than intended, resulting in sensitive data leaking in various contexts. For example, consider a sensitive environment variable passed to the `sh` step. [... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.03985585644841194,
0.034230370074510574,
-0.018002191558480263,
-0.034490346908569336,
-0.03142329305410385,
-0.048323120921850204,
-0.020380379632115364,
0.05635640770196915,
0.009597265161573887,
-0.008560724556446075,
-0.06956809014081955,
-0.09007634967565536,
0.03757866844534874,
-... | -0.081187 |
{ stage('Example') { steps { /\* WRONG! \*/ bat "echo ${EXAMPLE\_KEY}" } } } } // Script // ---- Here, the `bat` step receives `echo sec%ret` and the Windows batch shell will simply drop the `%` and print out the value `secret`. Because there is a single character difference, the value `secret` will not be masked. Thou... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.025445200502872467,
0.05476556718349457,
-0.06082606315612793,
0.03764684125781059,
-0.10114897042512894,
0.05041872709989548,
0.037754736840724945,
0.04206053540110588,
-0.02281438373029232,
0.01545198354870081,
-0.048257824033498764,
-0.12961441278457642,
0.053480684757232666,
0.01166... | -0.018403 |
executing builds/tests across multiple platforms. In the example below, the "Build" stage will be performed on one agent and the built results will be reused on two subsequent agents, labelled "linux" and "windows" respectively, during the "Test" stage. [pipeline] ---- // Declarative // pipeline { agent none stages { s... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
0.03572056069970131,
0.010025211609899998,
-0.043970417231321335,
-0.0365280918776989,
0.009465042501688004,
-0.029206348583102226,
-0.07079478353261948,
0.0013840304454788566,
0.0038228861521929502,
-0.04260144382715225,
0.050383951514959335,
-0.06323515623807907,
0.026928015053272247,
-0... | 0.04749 |
.. snip .. \*/ } } } // Declarative not yet implemented // ---- Instead of executing the tests on the "linux" and "windows" labelled nodes in series, they will now execute in parallel assuming the requisite capacity exists in the Jenkins environment. | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.050347886979579926,
-0.025339310988783836,
0.0027385996654629707,
0.013492755591869354,
0.04430830851197243,
-0.06715498864650726,
-0.08344952762126923,
-0.05491717904806137,
-0.018556348979473114,
-0.002340832492336631,
0.01651197299361229,
-0.06987334787845612,
0.013545521534979343,
-... | 0.115976 |
= Pipeline This chapter covers all recommended aspects of Jenkins Pipeline functionality, including how to: \* xref:blueocean:getting-started.adoc[get started with Pipeline] - covers how to xref:pipeline:getting-started.adoc#defining-a-pipeline[define a Jenkins Pipeline] (i.e. your `Pipeline`) through xref:pipeline:get... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/index.adoc | main | jenkins | [
-0.05289866030216217,
-0.06516566127538681,
-0.039972491562366486,
-0.024281123653054237,
0.0026648775674402714,
-0.0996624156832695,
0.003972184844315052,
0.00030574892298318446,
-0.06643944978713989,
-0.047153644263744354,
-0.01586001366376877,
-0.0941670760512352,
-0.03296542540192604,
... | 0.049229 |
span from simple continuous integration to comprehensive CD pipelines. By modeling a series of related tasks, users can take advantage of the many features of Pipeline: \* \*Code\*: Pipelines are implemented in code and typically checked into source control, giving teams the ability to edit, review, and iterate upon th... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/index.adoc | main | jenkins | [
-0.1328858584165573,
-0.018005913123488426,
0.017827995121479034,
-0.00801051501184702,
-0.056011978536844254,
-0.07141087204217911,
-0.05412988364696503,
0.019322872161865234,
0.027558911591768265,
-0.02530871331691742,
-0.028760163113474846,
0.0012341812252998352,
-0.02353038266301155,
-... | 0.19395 |
stages, on any available agent. <2> Defines the "Build" stage. <3> Perform some steps related to the "Build" stage. <4> Defines the "Test" stage. <5> Perform some steps related to the "Test" stage. <6> Defines the "Deploy" stage. <7> Perform some steps related to the "Deploy" stage. [#scripted-pipeline-fundamentals] ==... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/index.adoc | main | jenkins | [
-0.04491320624947548,
-0.0021326588466763496,
-0.017409037798643112,
0.038982272148132324,
0.015129323117434978,
-0.08288326114416122,
-0.11330084502696991,
0.0044732470996677876,
0.0019715118687599897,
0.016672439873218536,
-0.025936203077435493,
-0.04647066816687584,
-0.001307702623307705,... | 0.083089 |
(provided by the {plugin}junit[JUnit plugin]) for aggregating test reports. Read more about Pipeline syntax on the xref:pipeline:syntax.adoc[Pipeline Syntax] page. | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/index.adoc | main | jenkins | [
0.004985901992768049,
-0.04135708138346672,
-0.058028098195791245,
0.04752224683761597,
-0.04766056686639786,
0.04715701565146446,
-0.0307434294372797,
0.06804745644330978,
-0.09110621362924576,
-0.024757251143455505,
0.022847307845950127,
-0.04768594354391098,
0.03223287686705589,
0.02677... | 0.040592 |
= Pipeline as Code \_Pipeline as Code\_ describes a set of features that allow Jenkins users to define pipelined job processes with code, stored and versioned in a source repository. These features allow Jenkins to discover, manage, and run jobs for multiple source repositories and branches -- eliminating the need for ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-as-code.adoc | main | jenkins | [
-0.0552731528878212,
-0.09665869176387787,
-0.05078412964940071,
0.024716904386878014,
-0.029832972213625908,
-0.05034186691045761,
-0.05014008283615112,
-0.024578984826803207,
-0.006768469233065844,
-0.0029617473483085632,
-0.045865498483181,
-0.013298798352479935,
-0.0035566759761422873,
... | 0.163954 |
is available from this page. If folder computation doesn't result in an expected set of repositories, the log may have useful information to diagnose the problem. [role="image-border"] image::folder-computation-log.png[scaledwidth="75%",width="75%"] == Configuration Both \_Multibranch Pipeline\_ projects and \_Organiza... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-as-code.adoc | main | jenkins | [
-0.009278951212763786,
-0.055705927312374115,
-0.07421275973320007,
-0.0058541204780340195,
0.0031099726911634207,
-0.09186999499797821,
-0.0021866338793188334,
0.029576830565929413,
0.08872663974761963,
0.07372628897428513,
0.04137987270951271,
-0.028979873284697533,
0.052649497985839844,
... | 0.001075 |
new repositories. To create an \_Organization Folder\_ in Jenkins, go to: \*New Item -> GitHub Organization\* or \*New Item -> Bitbucket Team\* and follow the configuration steps for each item, making sure to specify appropriate \_Scan Credentials\_ and a specific \*owner\* for the GitHub Organization or Bitbucket Team... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-as-code.adoc | main | jenkins | [
-0.07042992860078812,
-0.0633784830570221,
-0.05307653918862343,
0.03877504542469978,
0.007836257107555866,
-0.05023183673620224,
0.000984741491265595,
-0.06598687171936035,
0.09375863522291183,
0.04615211859345436,
0.03336092084646225,
-0.021366003900766373,
0.06699241697788239,
0.0206921... | 0.085699 |
between development and operations teams. Many organizations have been orchestrating pipelines with existing Jenkins plugins for several years. As their automation sophistication and their own Jenkins experience increases, organizations inevitably want to move beyond simple pipelines and create complex flows specific t... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-as-code.adoc | main | jenkins | [
-0.055263977497816086,
-0.044057056307792664,
0.002365491818636656,
-0.013346973806619644,
-0.051832057535648346,
-0.06036211550235748,
-0.08590628206729889,
0.028006253764033318,
0.07517825812101364,
-0.005662580020725727,
-0.09804139286279678,
0.01578700542449951,
-0.01015249639749527,
0... | 0.184598 |
something that is ultimately discovered to be broken. [[throttled-concurrent]] .Throttled stage concurrency with Pipeline image::stage-concurrency.png[scaledwidth="90%"] Consider a simple pipeline with three stages. A naive implementation of this pipeline can sequentially trigger each stage on every commit. Thus, the d... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-as-code.adoc | main | jenkins | [
0.021952897310256958,
-0.0031693773344159126,
0.0534358024597168,
0.0023283816408365965,
-0.0032016767654567957,
-0.10567153990268707,
-0.07995916903018951,
-0.06409034132957458,
0.026308206841349602,
-0.05477205291390419,
0.054024823009967804,
-0.037938132882118225,
0.02636784315109253,
-... | -0.02705 |
the pipeline. This can enable users to debug which tests are failing at which stage or if there are other problems in their pipeline. Many organization also want to make their pipelines user-friendly for non-developers without having to develop a homegrown UI, which can prove to be a lengthy and ongoing development eff... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/pipeline-as-code.adoc | main | jenkins | [
-0.042269036173820496,
0.0461849644780159,
0.010520325973629951,
-0.00014780729543417692,
0.019840693101286888,
-0.04880860447883606,
-0.11039980500936508,
0.020960405468940735,
-0.007421284914016724,
-0.029908640310168266,
-0.0833914577960968,
-0.06385758519172668,
-0.04098163917660713,
0... | 0.06185 |
= Pipeline syntax This section builds on the information introduced in xref:pipeline:getting-started.adoc[Getting started with Pipeline] and should be treated solely as a reference. For more information on how to use Pipeline syntax in practical examples, refer to the xref:jenkinsfile.adoc[Using a Jenkinsfile] section ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.06185110658407211,
-0.05233898386359215,
-0.0163135789334774,
-0.03272179886698723,
-0.03071984276175499,
-0.08831658214330673,
-0.0035727673675864935,
0.02806279994547367,
-0.037554219365119934,
-0.05311797931790352,
-0.025329280644655228,
-0.06302524358034134,
-0.04364433512091637,
-0... | 0.065451 |
conditions. In this case, when using `timeout`, it is applied \*before\* the `agent` is allocated. The time to allocate the agent \*is included\* in the limit set by the `timeout` option. [source,groovy] ---- pipeline { agent none stages { stage('Example') { agent any options { // Timeout counter starts BEFORE agent is... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.01114314142614603,
0.043671660125255585,
-0.08114565163850784,
-0.03746859356760979,
-0.03869602829217911,
-0.02850072644650936,
-0.04201524332165718,
-0.0031280561815947294,
0.009131883271038532,
-0.0418119840323925,
0.006531377788633108,
-0.006230207625776529,
-0.028728198260068893,
-... | 0.045643 |
agent { // Equivalent to "docker build -f Dockerfile.build --build-arg version=1.0.2 ./build/ dockerfile { filename 'Dockerfile.build' dir 'build' label 'my-defined-label' additionalBuildArgs '--build-arg version=1.0.2' args '-v /tmp:/tmp' } } ---- + `dockerfile` also optionally accepts a `registryUrl` and `registryCre... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.007687028497457504,
0.017329223453998566,
-0.07894239574670792,
-0.052150972187519073,
-0.07835337519645691,
0.023577695712447166,
0.03598085418343544,
0.05265990272164345,
0.02014758624136448,
0.004480717703700066,
-0.0627472847700119,
-0.14717450737953186,
0.03910907730460167,
0.01174... | -0.001375 |
sh 'mvn --version' } } stage('Example Test') { agent { docker 'openjdk:21-jre' } // <3> steps { echo 'Hello, JDK' sh 'java -version' } } } } ---- <1> Defining `agent none` at the top-level of the Pipeline ensures that xref:user-docs:glossary:index.adoc#executor[ an Executor] will not be assigned unnecessarily. Using `a... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.034585822373628616,
0.04747726395726204,
-0.02685111202299595,
-0.07156671583652496,
-0.03283289074897766,
-0.07007290422916412,
-0.047318875789642334,
-0.0024443035945296288,
-0.013338634744286537,
-0.02658068574965,
-0.0024968793150037527,
-0.08651743084192276,
0.036157697439193726,
-... | 0.033963 |
steps] the same as the xref:#steps[steps] section. ===== [#stages] ==== stages Containing a sequence of one or more <> directives, the `stages` section is where the bulk of the "work" described by a Pipeline will be located. At a minimum, it is recommended that `stages` contain at least one <> directive for each discre... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.023121457546949387,
-4.5857035502194776e-8,
-0.06871794909238815,
-0.05492657795548439,
0.003082740819081664,
-0.03962095081806183,
-0.0075080436654388905,
0.012582956813275814,
-0.07273098826408386,
-0.05594616383314133,
-0.0005902759148739278,
-0.057354092597961426,
0.014038204215466976... | -0.006974 |
SERVICE\_CREDS = credentials('my-predefined-username-password') } steps { sh 'echo "Service user is $SERVICE\_CREDS\_USR"' sh 'echo "Service password is $SERVICE\_CREDS\_PSW"' sh 'curl -u $SERVICE\_CREDS https://myservice.example.com' } } stage('Example SSH Username with private key') { environment { SSH\_CREDS = crede... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
0.0026757894083857536,
0.01284768059849739,
-0.058962929993867874,
-0.04564741998910904,
-0.08820226788520813,
0.01097946334630251,
-0.005827907007187605,
0.04995344206690788,
-0.0201214961707592,
0.02008126489818096,
-0.04056255519390106,
-0.082175612449646,
0.0077541363425552845,
0.02614... | -0.043675 |
parallel stages in the pipeline. For example: `options { parallelsAlwaysFailFast() }` disableRestartFromStage:: Completely disable option "Restart From Stage" visible in classic Jenkins UI and Blue Ocean as well. For example: `options { disableRestartFromStage() }`. This option can not be used inside of the stage. [NOT... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.03166946396231651,
0.04867495968937874,
0.043748222291469574,
0.023738911375403404,
0.0039537264965474606,
-0.007015233859419823,
-0.08168063312768936,
-0.03166491910815239,
-0.0017453533364459872,
-0.029972266405820847,
0.024423614144325256,
-0.036668747663497925,
-0.023300325497984886,
... | 0.014896 |
description: 'Enter a password') } stages { stage('Example') { steps { echo "Hello ${params.PERSON}" echo "Biography: ${params.BIOGRAPHY}" echo "Toggle: ${params.TOGGLE}" echo "Choice: ${params.CHOICE}" echo "Password: ${params.PASSWORD}" } } } } ---- ===== [NOTE] ==== A comprehensive list of available parameters is pe... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.07537426799535751,
0.018439576029777527,
-0.036667902022600174,
0.03212912008166313,
-0.007144553121179342,
-0.02315717376768589,
-0.00770152173936367,
-0.014226817525923252,
-0.011548953130841255,
-0.014717599377036095,
-0.05257032811641693,
-0.048432257026433945,
0.053124237805604935,
... | 0.042705 |
cycles such as `\\*/3` or `H/3` will not work consistently near the end of most months, due to variable month lengths. For example, `\*/3` will run on the 1st, 4th, …31st days of a long month, then again the next day of the next month. Hashes are always chosen in the 1-28 range, so `H/3` will produce a gap between runs... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.08640939742326736,
0.028079146519303322,
-0.013145366683602333,
-0.009017000906169415,
-0.04674718156456947,
-0.08620867878198624,
-0.07425066828727722,
0.01562730222940445,
0.009411560371518135,
-0.04170427471399307,
-0.0014994365628808737,
-0.01633439213037491,
0.061106082051992416,
-... | 0.060438 |
parameters provided as part of the `input` submission will be available in the environment for the rest of the `stage`. ===== Configuration options message:: Required. This will be presented to the user when they go to submit the `input`. id:: An optional identifier for this `input`. The default value is based on the `... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.002117437543347478,
0.013903719373047352,
-0.06503938883543015,
-0.014445247128605843,
-0.042448561638593674,
-0.004221644252538681,
0.005054717883467674,
0.015587511472404003,
-0.07680658996105194,
-0.08090362697839737,
-0.02613098919391632,
-0.1143328920006752,
0.06086460128426552,
0.... | 0.036298 |
caseSensitive: true }` changeRequest:: Executes the stage if the current build is for a "change request" (a.k.a. Pull Request on GitHub and Bitbucket, Merge Request on GitLab, Change in Gerrit, etc.). When no parameters are passed the stage runs on every change request, for example: `when { changeRequest() }`. + By add... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.06434725224971771,
0.05825403705239296,
0.040089331567287445,
-0.025397811084985733,
-0.013269268907606602,
-0.07363007962703705,
0.004675505217164755,
-0.011384731158614159,
0.0354788675904274,
0.046915169805288315,
-0.06890864670276642,
-0.08045628666877747,
0.04034045711159706,
-0.03... | 0.058424 |
the `agent` will only be entered if the `when` condition evaluates to true. ===== Evaluating `when` before the `input` directive By default, the when condition for a stage will not be evaluated before the input, if one is defined. However, this can be changed by specifying the `beforeInput` option within the when block... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.04069201648235321,
0.05792267993092537,
-0.018128812313079834,
0.018849976360797882,
-0.052783917635679245,
0.03808218240737915,
-0.011495042592287064,
-0.025208281353116035,
0.013818485662341118,
0.024983355775475502,
0.058372125029563904,
-0.01890692301094532,
-0.0046709319576621056,
... | 0.011898 |
branch 'testing' } options { lock label: 'testing-deploy-envs', quantity: 1, variable: 'deployEnv' } steps { echo "Deploying to ${deployEnv}" } } } } ---- ===== .`triggeredBy` ===== [source, groovy] ---- pipeline { agent none stages { stage('Example Build') { steps { echo 'Hello World' } } stage('Example Deploy') { whe... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.024770943447947502,
0.0026009229477494955,
-0.06378381699323654,
-0.0179316196590662,
-0.009408781304955482,
-0.014491815119981766,
-0.018191033974289894,
-0.074582040309906,
-0.02628651075065136,
-0.02741219848394394,
0.040965333580970764,
-0.05069039389491081,
0.005863874219357967,
-0... | -0.004771 |
} parallel { stage('Branch A') { agent { label "for-branch-a" } steps { echo "On Branch A" } } stage('Branch B') { agent { label "for-branch-b" } steps { echo "On Branch B" } } stage('Branch C') { agent { label "for-branch-c" } stages { stage('Nested 1') { steps { echo "In stage Nested 1 within Branch C" } } stage('Nes... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.00008521079871570691,
0.03823181986808777,
-0.0969962477684021,
-0.04324635490775108,
-0.05733273923397064,
0.007652548141777515,
-0.05069664865732193,
-0.019145824015140533,
0.0035253081005066633,
-0.0020759946200996637,
0.029901018366217613,
-0.04505893588066101,
0.030377699062228203,
... | 0.078192 |
stage('deploy') { // ... } } } ---- ===== .Two-axis with 12 cells (three by four) ===== [source, groovy] ---- matrix { axes { axis { name 'PLATFORM' values 'linux', 'mac', 'windows' } axis { name 'BROWSER' values 'chrome', 'edge', 'firefox', 'safari' } } stages { stage('build-and-test') { // ... } } } ---- ===== [#matr... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.040004801005125046,
0.09208645671606064,
-0.10285183042287827,
-0.023140924051404,
0.05359608307480812,
-0.07078758627176285,
-0.0038655574899166822,
-0.09613171964883804,
-0.03597867861390114,
-0.020577343180775642,
0.05337090790271759,
-0.020854080095887184,
0.018468430265784264,
-0.0... | -0.019322 |
} when { anyOf { expression { params.PLATFORM\_FILTER == 'all' } expression { params.PLATFORM\_FILTER == env.PLATFORM } } } axes { axis { name 'PLATFORM' values 'linux', 'windows', 'mac' } axis { name 'BROWSER' values 'firefox', 'chrome', 'safari', 'edge' } } excludes { exclude { axis { name 'PLATFORM' values 'linux' }... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
0.015158277004957199,
0.08495772629976273,
0.02027098461985588,
-0.041333891451358795,
0.06646814197301865,
-0.06723679602146149,
-0.037251416593790054,
-0.052309561520814896,
-0.02754778414964676,
-0.024289755150675774,
-0.013104899786412716,
-0.08392992615699768,
-0.00901162438094616,
-0... | -0.033374 |
https://issues.jenkins.io/browse/WEBSITE-267 https://issues.jenkins.io/browse/WEBSITE-289 //// In order to provide \_durability\_, which means that running Pipelines can survive a restart of the Jenkins xref:user-docs:glossary:index.adoc#controller[ controller], Scripted Pipeline must serialize data back to the control... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/syntax.adoc | main | jenkins | [
-0.0743316262960434,
-0.019887221977114677,
-0.013545237481594086,
-0.013466402888298035,
-0.05050282180309296,
-0.08449102193117142,
-0.07413626462221146,
-0.0007672025822103024,
0.026800021529197693,
-0.009001166559755802,
-0.035009365528821945,
0.02078896388411522,
-0.03768007829785347,
... | 0.00833 |
= Scaling Pipelines == Using Speed/Durability Settings To Reduce Disk I/O Needs One of the main bottlenecks in Pipeline is that it writes transient data to disk \*FREQUENTLY\* so that running pipelines can handle an unexpected Jenkins restart or system crash. This durability is useful for many users but its performance... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/scaling-pipeline.adoc | main | jenkins | [
-0.03845398500561714,
0.008623761124908924,
0.028647875413298607,
0.06457816809415817,
-0.030325382947921753,
-0.10680104047060013,
-0.0727749839425087,
0.06387607008218765,
0.0197304617613554,
0.011005843058228493,
-0.05999515950679779,
0.04994075000286102,
-0.040418270975351334,
-0.01326... | 0.097487 |
not using Pipelines, or your system is loaded down by other factors. \* No, if you don't enable higher-performance modes for pipelines. == What Am I Giving Up With This Durability Setting "Trade-Off?" \*Stability of Jenkins ITSELF is not changed regardless of this setting\* - it only applies to Pipelines. The worst-cas... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/scaling-pipeline.adoc | main | jenkins | [
-0.02604779414832592,
-0.00544934906065464,
0.0629509910941124,
0.022272754460573196,
-0.016653582453727722,
-0.0859575942158699,
-0.11703065782785416,
0.015049316920340061,
0.02663162164390087,
-0.025082463398575783,
-0.08186732977628708,
0.044656842947006226,
-0.04274456948041916,
-0.016... | 0.04652 |
Tips for Durability Settings \* Use the "performance-optimized" mode for most pipelines and especially basic build-test Pipelines or anything that can simply be run again if needed. \* Use either the "maximum durability" or "less durable" mode for pipelines when you need a guaranteed record of their execution (auditing... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/scaling-pipeline.adoc | main | jenkins | [
-0.06068599596619606,
-0.02055448293685913,
-0.04634550213813782,
0.011337719857692719,
-0.06125751510262489,
-0.1139056533575058,
-0.07000192999839783,
0.028508426621556282,
-0.0857723206281662,
-0.020805105566978455,
-0.03028283268213272,
0.0019711158238351345,
-0.012308855541050434,
-0.... | 0.026303 |
code by reducing the number of steps run and using simpler Groovy code for Scripted Pipelines. \* Consolidate sequential steps of the same type if you can, for example by using one Shell step to invoke a helper script rather than running many steps. \* Try to limit the amount of data written to logs by Pipelines. If yo... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/scaling-pipeline.adoc | main | jenkins | [
-0.035649094730615616,
0.0484950989484787,
0.02499140240252018,
-0.028144363313913345,
-0.028386618942022324,
-0.14615516364574432,
-0.07382725924253464,
0.010017639957368374,
0.04660912603139877,
0.04197220876812935,
-0.06657722592353821,
-0.01008699368685484,
-0.038509342819452286,
-0.03... | 0.052802 |
= Pipeline CPS Method Mismatches Jenkins Pipeline uses a library called Groovy CPS to run Pipeline scripts. While Pipeline uses the Groovy parser and compiler, unlike a regular Groovy environment it runs most of the program inside a special interpreter. This uses a continuation-passing style (CPS) transform to turn you... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/cps-method-mismatches.adoc | main | jenkins | [
-0.07099936902523041,
-0.0016317102126777172,
0.00314787938259542,
-0.039370857179164886,
0.00861493032425642,
-0.10325895249843597,
-0.06038631871342659,
-0.017990896478295326,
0.04149986431002617,
-0.03699084371328354,
-0.051796142011880875,
-0.01645679771900177,
-0.026336580514907837,
-... | -0.041176 |
'22']) echo(sorted.toString()) ---- The closure passed to `+Iterable.toSorted+` is CPS-transformed, but `+Iterable.toSorted+` itself is not CPS-transformed internally, so this will not work as intended. The current behavior is that the return value of the call to `toSorted` will be the return value of the first call to... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/cps-method-mismatches.adoc | main | jenkins | [
-0.034072328358888626,
0.025034897029399872,
-0.006501399911940098,
0.00904326606541872,
-0.017944805324077606,
-0.009277017787098885,
0.0735388994216919,
0.03142949566245079,
-0.016892658546566963,
-0.0036812913604080677,
-0.04169273003935814,
0.005069929175078869,
-0.014043322764337063,
... | 0.02867 |
in Pipeline scripts, this will not work as expected, because the closure inside of the GString will be CPS-transformed. Here is an example: [source,groovy] ---- def x = 1 def s = "x = ${-> x}" x = 2 echo(s) ---- Using a closure inside of a `+GString+` as in this example will not work. The warning from the logs when run... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/cps-method-mismatches.adoc | main | jenkins | [
-0.07678590714931488,
0.011184989474713802,
0.030803311616182327,
0.016138257458806038,
-0.07226928323507309,
-0.04242526739835739,
0.08354787528514862,
-0.0003018998831976205,
0.034611210227012634,
-0.08248893916606903,
-0.05620343238115311,
-0.07426594942808151,
0.005476567428559065,
-0.... | -0.054386 |
= Running multiple steps Pipelines are made up of multiple steps that allow you to build, test and deploy applications. Jenkins Pipeline allows you to compose multiple steps in an easy way that can help you model any sort of automation process. Think of a "step" like a single command which performs a single action. Whe... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/running-multiple-steps.adoc | main | jenkins | [
-0.034079983830451965,
-0.017493002116680145,
0.061752814799547195,
-0.020790427923202515,
-0.021728860214352608,
-0.07814768701791763,
-0.12427540123462677,
0.007078676484525204,
0.05345386639237404,
-0.012004693038761616,
-0.06570875644683838,
-0.03022690862417221,
0.016173649579286575,
... | 0.093213 |
clean-up steps or perform some actions based on the outcome of the Pipeline. These actions can be performed in the `post` section. [pipeline] ---- // Declarative // pipeline { agent any stages { stage('Test') { steps { sh 'echo "Fail!"; exit 1' } } } post { always { echo 'This will always run' } success { echo 'This wi... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/running-multiple-steps.adoc | main | jenkins | [
-0.021182339638471603,
0.05808504298329353,
0.009264410473406315,
0.03430977091193199,
-0.014330455102026463,
-0.04770740494132042,
-0.10041864216327667,
0.03769008815288544,
-0.04918321594595909,
-0.015601691789925098,
-0.04978485032916069,
-0.02688051387667656,
0.015323551371693611,
-0.0... | 0.073625 |
= Recording tests and artifacts While testing is a critical part of a good continuous delivery pipeline, most people don't want to sift through thousands of lines of console output to find information about failing tests. To make this easier, Jenkins can record and aggregate test results so long as your test runner can... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/tests-and-artifacts.adoc | main | jenkins | [
-0.004603040870279074,
0.057329095900058746,
-0.024829266592860222,
0.044828109443187714,
0.02117193676531315,
-0.009600858204066753,
-0.11310626566410065,
0.0181420985609293,
-0.015421166084706783,
-0.04826941713690758,
-0.01824682205915451,
-0.060904622077941895,
0.030212806537747383,
-0... | 0.026153 |
= Creating your first Pipeline == What is a Jenkins Pipeline? Jenkins Pipeline (or simply "Pipeline") is a suite of plugins which supports implementing and integrating \_continuous delivery pipelines\_ into Jenkins. A \_continuous delivery pipeline\_ is an automated expression of your process for getting software from ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/hello-world.adoc | main | jenkins | [
-0.05001087114214897,
-0.07820248603820801,
-0.04020488262176514,
0.02310587652027607,
-0.015567058697342873,
-0.060190390795469284,
-0.03168664872646332,
0.018378186970949173,
-0.006496017333120108,
-0.01262992899864912,
-0.026555942371487617,
-0.02365763857960701,
0.009335842914879322,
-... | 0.152834 |
docker.image('python:3.12.1-alpine3.19').inside { sh 'python --version' } } } ---- === PHP [pipeline] ---- // Declarative // /\* Requires the Docker Pipeline plugin \*/ pipeline { agent { docker { image 'php:8.3.7-alpine3.20' } } stages { stage('build') { steps { sh 'php --version' } } } } // Scripted // /\* Requires t... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/hello-world.adoc | main | jenkins | [
0.024555804207921028,
0.10046277940273285,
-0.0016288445331156254,
-0.04574200510978699,
0.018120603635907173,
-0.0186094231903553,
-0.07199327647686005,
-0.00741178123280406,
-0.0012469022767618299,
0.007093518972396851,
-0.04669059440493584,
-0.07227873802185059,
-0.006803999654948711,
0... | 0.007683 |
= Deployment The most basic continuous delivery pipeline will have, at minimum, three stages which should be defined in a `Jenkinsfile`: Build, Test, and Deploy. For this section we will focus primarily on the Deploy stage, but it should be noted that stable Build and Test stages are an important precursor to any deplo... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/deployment.adoc | main | jenkins | [
0.020651686936616898,
-0.009656723588705063,
-0.015431653708219528,
0.007273039780557156,
-0.016576062887907028,
-0.03110296092927456,
-0.08332197368144989,
-0.020132746547460556,
-0.006331374868750572,
-0.013723618350923061,
-0.005993949249386787,
-0.07635848224163055,
0.02014203742146492,
... | 0.058 |
= Defining execution environments In the xref:./running-multiple-steps.adoc[previous section] you may have noticed the `agent` directive in each of the examples. The `agent` directive tells Jenkins where and how to execute the Pipeline, or subset thereof. As you might expect, the `agent` is required for all Pipelines. ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/agents.adoc | main | jenkins | [
-0.06101541593670845,
-0.03447362408041954,
-0.029254600405693054,
-0.02617299184203148,
-0.022415412589907646,
-0.10804837942123413,
0.005121911410242319,
-0.028006212785840034,
0.027742542326450348,
-0.0006490882951766253,
-0.009569014422595501,
-0.07169602811336517,
-0.05085092782974243,
... | 0.024254 |
= Getting started with the Guided Tour This guided tour introduces you to the basics of using Jenkins and its main feature, Jenkins Pipeline. This tour uses the "standalone" Jenkins distribution, which runs locally on your own machine. [#prerequisites] == Prerequisites For this tour, you will require: \* A machine with... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/getting-started.adoc | main | jenkins | [
0.01889808475971222,
0.04543887451291084,
0.028260638937354088,
-0.016446661204099655,
-0.0442679338157177,
-0.046583566814661026,
-0.0785471498966217,
0.02283552847802639,
-0.013156397268176079,
-0.013231550343334675,
-0.10541187971830368,
-0.055769845843315125,
0.03451007977128029,
0.011... | 0.080394 |
= Using environment variables Environment variables can be set globally, like the example below, or per stage. As you might expect, setting environment variables per stage means they will only apply to the stage in which they're defined. [pipeline] ---- // Declarative // pipeline { agent { label '!windows' } environmen... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/environment.adoc | main | jenkins | [
0.04478435590863228,
0.02875877358019352,
-0.04201710969209671,
0.019686415791511536,
-0.01870952546596527,
-0.0037194194737821817,
0.04741837456822395,
-0.005418324843049049,
-0.07776616513729095,
-0.01131510641425848,
-0.05958674103021622,
-0.11620929837226868,
0.03796394541859627,
-0.03... | -0.029912 |
= Cleaning up and notifications Since the `post` section of a Pipeline is guaranteed to run at the end of a Pipeline's execution, we can add some notification or other steps to perform finalization, notification, or other end-of-Pipeline tasks. NOTE: See xref:user-docs:glossary:index.adoc#build-status[Glossary - Build ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/pipeline/pages/tour/post.adoc | main | jenkins | [
-0.04095494747161865,
-0.014443757943809032,
0.0527883805334568,
-0.030923377722501755,
-0.0357975997030735,
-0.09562565386295319,
0.03457837179303169,
-0.05546249449253082,
0.010840357281267643,
-0.008312933146953583,
-0.012431847862899303,
-0.056055035442113876,
0.0002943468280136585,
-0... | 0.020792 |
= Using Search Box Every page in Jenkins has a search box on its top right that lets you get to your destination quickly, without multiple clicks. [.boxshadow] image::search/box.png[image] For example, if you type "foo #53 console", you'll be taken to the console output page of the "foo" job build #53. If you have "XYZ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/searchbox.adoc | main | jenkins | [
0.019585803151130676,
0.017492491751909256,
0.027575939893722534,
0.07893488556146622,
0.07353932410478592,
-0.00579316820949316,
-0.035945236682891846,
-0.03993040323257446,
-0.025104714557528496,
-0.033710066229104996,
-0.06539016216993332,
0.0119180204346776,
0.03933326527476311,
0.0100... | -0.017866 |
= Using JMeter with Jenkins There are several advantages to using JMeter and Jenkins together. Continuous integration and test automation have become standards in the DevOps world, but the performance levels and system complexity are constantly increasing. With Jenkins, you can integrate all JMeter tests in your pipeli... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-jmeter-with-jenkins.adoc | main | jenkins | [
-0.05238638073205948,
-0.010306483134627342,
-0.04221015423536301,
0.06639562547206879,
-0.03902086615562439,
-0.06261986494064331,
-0.08059414476156235,
-0.005857448559254408,
0.02677800878882408,
-0.04630376771092415,
-0.05219076946377754,
-0.06451985985040665,
-0.009338730946183205,
0.0... | 0.130847 |
Windows users the file will be `jmeter.bat`. . From the JMeter GUI, go to \*File\*, and then select \*New\*. . Enter a name for your test plan. . On the left side of the screen, using the right or secondary select with your mouse, select your test plan. Follow this path: \*Add > Thread(Users) > Thread Group\*, and sele... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-jmeter-with-jenkins.adoc | main | jenkins | [
-0.0475589744746685,
0.025190167129039764,
-0.038573164492845535,
0.023407509550452232,
-0.03840891271829605,
-0.032685376703739166,
-0.03624250367283821,
0.003507135668769479,
-0.010953953489661217,
0.04077201709151268,
-0.02567259967327118,
-0.05356740206480026,
0.004570472054183483,
0.0... | 0.003544 |
you can access the \*Performance Report\*, and can view the JMeter report data. + image::jmeter/jmeter-13.png[Report Execution Details] You now have JMeter running within Jenkins, and can use the data provided. | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-jmeter-with-jenkins.adoc | main | jenkins | [
0.013897785916924477,
0.05567469820380211,
-0.05633207783102989,
0.08598076552152634,
0.03258492052555084,
-0.019988803192973137,
-0.05906767025589943,
-0.0035660038702189922,
-0.026254339143633842,
-0.01636296696960926,
-0.041993647813797,
-0.04887901246547699,
0.025948502123355865,
0.029... | 0.031872 |
:page-aliases: sigs:cloud-native:pluggable-storage.adoc = Pluggable Storage The current default approach of storing everything into the filesystem is the main reason why Jenkins does not fit the "Cloud Native" model, with features like high availability, zero downtime, or pay per use. While there are plenty of plugins ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/pluggable-storage.adoc | main | jenkins | [
-0.04481973499059677,
0.013969768770039082,
0.04513682797551155,
0.04051489382982254,
-0.005454425700008869,
-0.04100373387336731,
-0.05128942430019379,
0.02774708904325962,
0.0269013624638319,
0.07016151398420334,
-0.03504326567053795,
0.030733248218894005,
0.0037503810599446297,
0.007258... | 0.081604 |
link:https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin[PostgreSQL (unreleased)] | Workspaces + (Not started) | Proposed as a GSoC 2019 project: xref:projects:gsoc:2019/project-ideas/ext-workspace-manager-cloud-features.adoc[Cloud Features for External Workspace Manager Plugin] | N/A |==================... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/pluggable-storage.adoc | main | jenkins | [
-0.08700540661811829,
-0.045876968652009964,
-0.03365309163928032,
0.04188264533877373,
0.0010665197623893619,
-0.03350217640399933,
-0.0008995229145511985,
-0.0352427214384079,
-0.029925091192126274,
0.041492052376270294,
0.024073205888271332,
0.008504356257617474,
-0.010675603523850441,
... | 0.060644 |
plugin. Please try it out, report issues to link:https://github.com/jenkinsci/junit-plugin/issues[GitHub] and general feedback to link:https://github.com/jenkinsci/junit-plugin/issues/142[GitHub#142]. === Fingerprints The fingerprints are stored within `JENKINS\_HOME` inside a local XML-based database. Externalizing fi... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/pluggable-storage.adoc | main | jenkins | [
-0.14662232995033264,
0.0383472703397274,
-0.03365696594119072,
-0.025175239890813828,
0.0432046614587307,
-0.04284542053937912,
-0.053886234760284424,
-0.032578613609075546,
0.004504762589931488,
-0.029032627120614052,
0.04963347315788269,
0.010993413627147675,
0.03502736613154411,
-0.024... | 0.08887 |
= Referencing another project by name In many places throughout Jenkins, you can refer to another project/job by name. For example, in a Pipeline Script, you might want to {plugin}copyartifact/[copy artifacts] from another project: .... copyArtifacts projectName: 'myproject' .... That's all you need to do if your targe... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/referencing-another-project-by-name.adoc | main | jenkins | [
-0.07482488453388214,
-0.058046430349349976,
-0.02431996911764145,
-0.0061662569642066956,
0.023509521037340164,
-0.019302887842059135,
0.059177465736866,
-0.02978128008544445,
0.07604862004518509,
-0.018911175429821014,
0.004846600815653801,
-0.09868576377630234,
0.053273387253284454,
0.0... | 0.058812 |
= Working with projects Jenkins uses projects (also known as "jobs") to perform its work. Projects are defined and run by Jenkins users. Jenkins offers several different types of projects, including: \* xref:pipeline:index.adoc[Pipeline] \* xref:pipeline:multibranch.adoc[Multibranch Pipeline] \* xref:pipeline:multibran... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/working-with-projects.adoc | main | jenkins | [
-0.09604620933532715,
-0.10536573827266693,
-0.04949091374874115,
-0.009140605106949806,
0.06853976845741272,
-0.0853777825832367,
-0.02936636283993721,
-0.0633702501654625,
0.05547057464718819,
-0.06364719569683075,
-0.005130706820636988,
-0.06533104181289673,
-0.025155091658234596,
0.008... | 0.077847 |
= Best Practices Continuous Integration (CI) with automated test execution and trend analysis has revolutionized the way companies approach build management, release management, deployment automation, and test orchestration. In this section, we will explore best practices that aim to enlighten executives, business mana... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/best-practices.adoc | main | jenkins | [
-0.04688262566924095,
-0.01018615160137415,
-0.04520830512046814,
0.024816349148750305,
-0.04614682495594025,
-0.08282483369112015,
-0.047410886734724045,
-0.031098226085305214,
-0.01981024630367756,
-0.014367984607815742,
-0.03237145394086838,
-0.0319657027721405,
0.011024637147784233,
0.... | 0.127314 |
builds on the controller. Utilizing agents offers enhanced safety and scalability. Refer to the xref:user-docs:security:controller-isolation.adoc[controller isolation] documentation for more details. === Show failures to the right people Configure notifications for failing and unstable jobs, to ensure that the right pe... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/best-practices.adoc | main | jenkins | [
-0.03632650524377823,
-0.07899649441242218,
-0.019614942371845245,
0.042976077646017075,
0.06971660256385803,
-0.09123965352773666,
0.05999516323208809,
0.0011098362738266587,
0.051632899791002274,
0.027179304510354996,
-0.008912482298910618,
-0.03387320041656494,
0.021047895774245262,
0.0... | 0.095915 |
availability of your data. Regularly testing your backups and verifying their completeness and restorability will help you mitigate the impact of any potential failures and ensure that your data can be recovered effectively when needed. Prioritizing backup health and conducting routine checks is essential for maintaini... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/best-practices.adoc | main | jenkins | [
-0.09160739183425903,
-0.007394594140350819,
-0.016647178679704666,
0.02263006567955017,
0.024050014093518257,
-0.07060926407575607,
-0.0003090029931627214,
0.002715997165068984,
-0.03170445188879967,
-0.016105106100440025,
-0.05295823886990547,
0.0353999026119709,
-0.01684582233428955,
-0... | 0.085242 |
:page-aliases: user-docs:using-jenkins:remote-api.adoc = Remote Access API Jenkins provides machine-consumable remote access API to its functionalities. Currently it comes in three flavors: . XML . JSON with JSONP support . Python Remote access API is offered in a REST-like style. That is, there is no single entry poin... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/remote-access-api.adoc | main | jenkins | [
-0.05402863398194313,
0.0445440337061882,
0.004344640299677849,
0.01948748528957367,
0.014562755823135376,
-0.04611179605126381,
-0.08341473340988159,
-0.00761677511036396,
0.017245681956410408,
-0.03097800351679325,
-0.04732609912753105,
0.012564214877784252,
0.02251608297228813,
-0.02214... | 0.078994 |
at the object for which you made a remote API call, and the sub-tree is cut beyond certain depth to avoid returning too much data. You can adjust this cut-off behavior by specifying the depth query parameter. When you specify a positive depthvalue, the subtree cut-off happens that much later. So the net result is, if y... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/remote-access-api.adoc | main | jenkins | [
-0.05858416482806206,
0.06019365042448044,
0.07969924062490463,
0.029864013195037842,
0.0033539931755512953,
-0.1733303666114807,
-0.11399994045495987,
0.005085591692477465,
0.07296521961688995,
0.04363708943128586,
-0.07843045145273209,
-0.04051515460014343,
-0.003955690190196037,
-0.0272... | -0.030112 |
include: \* Endpoint definition (property or environment variable) \* Authentication (basic and API token via property or environment variable) \* Crumbs Issuer support (auto-detect crumbs) \* Folder support \* Jobs API (build, buildInfo, buildWithParameters, config, create, delete, description, disable, enable, jobInf... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/remote-access-api.adoc | main | jenkins | [
-0.03136985003948212,
-0.03640618547797203,
-0.00842125155031681,
0.01729605719447136,
0.007245185319334269,
-0.05334144085645676,
-0.07150008529424667,
0.0285011176019907,
0.0016970786964520812,
0.02958722971379757,
-0.015095295384526253,
-0.05878060683608055,
0.0031389377545565367,
0.013... | 0.158959 |
= Change time zone If your Jenkins controller is running in a different location than your own (for example: the server is in NY but you are in LA), then the NY time zone will most probably be used. This may be quite annoying if you need to compare build dates. To see the time zone currently set, go to `jenkins\_server... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/change-time-zone.adoc | main | jenkins | [
0.05370815843343735,
0.02241082303225994,
0.0533759780228138,
0.002062732120975852,
0.046788740903139114,
-0.0277932770550251,
-0.10421070456504822,
-0.0412273071706295,
0.050591833889484406,
0.01793767884373665,
-0.06842181086540222,
-0.011961264535784721,
-0.03341704234480858,
0.00991768... | -0.06972 |
= Using credentials There are numerous 3rd-party sites and applications that can interact with Jenkins, for example, artifact repositories, cloud-based storage systems and services, and so on. A systems administrator of such an application can configure credentials in the application for dedicated use by Jenkins. This ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-credentials.adoc | main | jenkins | [
-0.06946010142564774,
-0.05690254271030426,
-0.08272597938776016,
-0.053569480776786804,
-0.04656010866165161,
-0.03416789695620537,
0.004969589877873659,
0.005300904158502817,
0.05928237736225128,
-0.03546591103076935,
-0.08070629835128784,
-0.037461694329977036,
0.02782895788550377,
0.03... | 0.099488 |
(which is the same as clicking the \*Add Credentials\* link). . From the \*Kind\* field, choose the xref:#types-of-credentials[type of credentials] to add. . From the \*Scope\* field, choose either: \* \*Global\* - if the credential/s to be added is/are for a Pipeline project/item. Choosing this option applies the scop... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-credentials.adoc | main | jenkins | [
-0.06141679733991623,
-0.057465795427560806,
-0.06100485473871231,
-0.01131702121347189,
-0.03535725921392441,
0.00404069060459733,
0.014884764328598976,
0.020737456157803535,
0.06151739880442619,
0.036304473876953125,
-0.09857470542192459,
-0.10922165960073471,
0.057983286678791046,
0.017... | -0.046279 |
= Fingerprints == Tracking file usage across Jenkins jobs using fingerprints When you have interdependent projects on Jenkins, it often becomes hard to keep track of which version of a file is used by which version of a dependency on that file. Jenkins supports \*file fingerprinting\* to track dependencies. For example... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/fingerprints.adoc | main | jenkins | [
-0.07010789215564728,
0.025165613740682602,
0.07727969437837601,
-0.0219216700643301,
0.11977504193782806,
-0.06548390537500381,
-0.006667630281299353,
-0.06824037432670593,
0.02901533804833889,
-0.002017990220338106,
-0.047199368476867676,
-0.018238361924886703,
-0.012054000981152058,
0.0... | 0.039744 |
you are using in TOP #10. . Go to TOP #10 build page. . Click "see fingerprints" . You'll see all the files fingerprinted in TOP #10, along with where they came from. You have the TOP project that builds a jar. You also have the TOP-TEST project that runs after the TOP project and does extensive integration tests on th... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/fingerprints.adoc | main | jenkins | [
-0.05712525174021721,
-0.03131893649697304,
0.028592385351657867,
-0.03242620453238487,
0.14648297429084778,
-0.039161890745162964,
-0.050511814653873444,
0.018215829506516457,
-0.018654031679034233,
0.014575265347957611,
0.026313208043575287,
-0.01102074608206749,
0.010539797134697437,
-0... | 0.027496 |
= Using Jenkins agents The Jenkins architecture is designed for distributed build environments. It allows us to use different environments for each build project balancing the workload among multiple agents running jobs in parallel. The Jenkins controller is the original node in the Jenkins installation. The Jenkins co... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-agents.adoc | main | jenkins | [
-0.01980443298816681,
0.011401508934795856,
-0.04845874756574631,
-0.008689074777066708,
-0.0155546385794878,
-0.036365289241075516,
-0.07907801866531372,
-0.05728458985686302,
0.0552176907658577,
0.0038763992488384247,
-0.08460928499698639,
-0.04336869344115257,
0.054420653730630875,
-0.0... | 0.142769 |
insert the content of your private key file at `~/.ssh/jenkins\_agent\_key` \* Passphrase: fill your passphrase used to generate the SSH key pair (leave empty if you didn't use one at the previous step) and then press the `Create` button image:node/credentials-3.png[credentials filled form,650] === Creating your Docker... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-agents.adoc | main | jenkins | [
0.024759575724601746,
0.0051405043341219425,
-0.07204752415418625,
-0.0023708599619567394,
-0.024898884817957878,
-0.0013853732962161303,
-0.06705676019191742,
-0.011417368426918983,
0.012553668580949306,
0.017600063234567642,
-0.05323057994246483,
-0.07855387032032013,
0.09001907706260681,
... | -0.005584 |
successfully connected,650] If your Jenkins controller does not start the agent via ssh, please check the port you xref:#ssh-anchor[configured] on your agent. Copy it, and then click on the `Advanced...` button. You will then be able to paste the port number into the `Port` textfield. === Delegating the first job to ag... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/using-agents.adoc | main | jenkins | [
0.00819744449108839,
-0.029796598479151726,
-0.0744255930185318,
-0.012901920825242996,
0.028062907978892326,
-0.005887791980057955,
-0.048263706266880035,
-0.04232993349432945,
-0.005118145607411861,
-0.003509428584948182,
-0.012386290356516838,
-0.039983004331588745,
0.02201530709862709,
... | -0.028222 |
= Using Jenkins This chapter contains topics for typical Jenkins users (of all skill levels) about Jenkins usage which is outside the scope of the core Jenkins features: Pipeline and Blue Ocean. If you want to create and configure a Pipeline project through a `Jenkinsfile` or through Blue Ocean, or you wish to find out... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/index.adoc | main | jenkins | [
-0.009703434072434902,
-0.07152768969535828,
-0.037198759615421295,
0.0356530137360096,
0.01061477605253458,
-0.07703640311956406,
-0.016729308292269707,
0.006479084026068449,
-0.0649709478020668,
-0.025307172909379005,
-0.06018108129501343,
-0.018144730478525162,
0.0028611039742827415,
-0... | 0.133279 |
= Executor Starvation If you see a little black clock icon in the build queue as shown below, it is an indication that your job is sitting in the queue unnecessarily. image::starvation.png[image,title="Starvation"] The tool tip of the job name link next to the clock icon should tell you exactly why it is not building, ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/executor-starvation.adoc | main | jenkins | [
-0.042796071618795395,
0.022616174072027206,
-0.01751422882080078,
0.027424577623605728,
0.04342033341526985,
-0.08481121808290482,
-0.06471408158540726,
-0.08429085463285446,
0.056393783539533615,
0.006381012499332428,
-0.028553318232297897,
-0.07468394935131073,
-0.031024662777781487,
-0... | 0.049204 |
= Aborting a build When you click that [x] icon from the UI, the following things happen: . Browser sends a request to the server. . The server interrupts (via Thread.interrupt()) the thread (AKA executor thread) that is responsible for carrying out a build. . The server returns At this point, your browser is back, but... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/using-jenkins/pages/aborting-a-build.adoc | main | jenkins | [
-0.06655273586511612,
0.022088253870606422,
0.016531698405742645,
-0.0022147265262901783,
0.054894573986530304,
-0.11201606690883636,
-0.00841785129159689,
-0.013868681155145168,
0.06729907542467117,
0.0008792273583821952,
0.06272043287754059,
0.004975473508238792,
-0.06073799729347229,
-0... | 0.151588 |
= Permissions // TODO add some more permissions The following sections describe the access granted to users with (or without) the specified permissions. == Default Permissions === \_Overall\_ Permissions These permissions are granted globally, rather than on individual objects. ==== Access granted \_without\_ Overall/R... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main/docs/user-docs/modules/security/pages/permissions.adoc | main | jenkins | [
-0.027582639828324318,
0.04143800958991051,
-0.01537053007632494,
0.011097501963376999,
-0.010266789235174656,
-0.043949324637651443,
-0.01857316866517067,
0.024771185591816902,
-0.024413473904132843,
-0.013013792224228382,
-0.050879865884780884,
-0.047802481800317764,
0.02460593730211258,
... | 0.14067 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.