-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
I would like to have a possibility to set/change the default execution node (currently: master) of Jenkins pipeline jobs. It is not about the node used for the execution of the Jenkinsfile. It is about the node where the job execution starts. This is because we are using Jenkins with many different teams and I would like to prevent any job executions on the master node.
The job is always trying to start on the master node. Why?
UPDATE:
Over the NodeLabel Parameter Plugin (as job parameter) I was able to change this behavior, but it would be very nice if there will be another way to change it!
I will be very happy to receive any help or feedback about this feature.
Best regards,
Nikolay
[JENKINS-51978] Change default execution node of pipeline jobs
Nikolay Nachev
created issue -
Nikolay Nachev
made changes -
| Attachment | New: screenshot-1.png [ 42892 ] |
Nikolay Nachev
made changes -
| Description |
Original:
I would like to have a possibility to set/change the default checkout node (currently: *master*) of the Jenkins shared library. This is because we are using Jenkins with many different teams and I would like to prevent any job executions on the master node. {code:java} @Library('my-shared-library') _ // <- it is about this step here .... node("some_node_label") { ... } {code} Even if the pipeline is using another node for the execution the checkout always happens on the master node. I will be very happy to receive any help or feedback about this feature. Best regards, Nikolay |
New:
I would like to have a possibility to set/change the default checkout node (currently: *master*) of the Jenkins shared library. This is because we are using Jenkins with many different teams and I would like to prevent any job executions on the master node. {code:java} @Library('my-shared-library') _ // <- it is about this step here .... node("some_node_label") { ... } {code} Even if the pipeline is using another node for the execution the checkout always happens on the master node. I tried to move the @Library annotation within the node close but this also doesn't help me: {code} node("some_node_label") { @Library('my-shared-library') _ ... } {code} The job is always trying to start on the master node. Why? !screenshot-1.png|thumbnail! I will be very happy to receive any help or feedback about this feature. Best regards, Nikolay |
Nikolay Nachev
made changes -
| Component/s | New: workflow-api-plugin [ 21711 ] |
Nikolay Nachev
made changes -
| Description |
Original:
I would like to have a possibility to set/change the default checkout node (currently: *master*) of the Jenkins shared library. This is because we are using Jenkins with many different teams and I would like to prevent any job executions on the master node. {code:java} @Library('my-shared-library') _ // <- it is about this step here .... node("some_node_label") { ... } {code} Even if the pipeline is using another node for the execution the checkout always happens on the master node. I tried to move the @Library annotation within the node close but this also doesn't help me: {code} node("some_node_label") { @Library('my-shared-library') _ ... } {code} The job is always trying to start on the master node. Why? !screenshot-1.png|thumbnail! I will be very happy to receive any help or feedback about this feature. Best regards, Nikolay |
New:
I would like to have a possibility to set/change the default checkout node (currently: *master*) of the Jenkins shared library. This is because we are using Jenkins with many different teams and I would like to prevent any job executions on the master node. {code:java} @Library('my-shared-library') _ // <- it is about this step here .... node("some_node_label") { ... } {code} Even if the pipeline is using another node for the execution the checkout always happens on the master node. I tried to move the @Library annotation within the node close but this also doesn't help me: {code:java} node("some_node_label") { @Library('my-shared-library') _ ... } {code} The job is always trying to start on the master node. Why? !screenshot-1.png|thumbnail! UPDATE: Over the [NodeLabel Parameter Plugin|https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin] (as job parameter) I was able to change this behavior, but it would be very nice if there will be another way to change it! I will be very happy to receive any help or feedback about this feature. Best regards, Nikolay |
Nikolay Nachev
made changes -
| Summary | Original: Change default checkout node of the shared-library | New: Change default execution node of pipeline jobs |
Nikolay Nachev
made changes -
| Description |
Original:
I would like to have a possibility to set/change the default checkout node (currently: *master*) of the Jenkins shared library. This is because we are using Jenkins with many different teams and I would like to prevent any job executions on the master node. {code:java} @Library('my-shared-library') _ // <- it is about this step here .... node("some_node_label") { ... } {code} Even if the pipeline is using another node for the execution the checkout always happens on the master node. I tried to move the @Library annotation within the node close but this also doesn't help me: {code:java} node("some_node_label") { @Library('my-shared-library') _ ... } {code} The job is always trying to start on the master node. Why? !screenshot-1.png|thumbnail! UPDATE: Over the [NodeLabel Parameter Plugin|https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin] (as job parameter) I was able to change this behavior, but it would be very nice if there will be another way to change it! I will be very happy to receive any help or feedback about this feature. Best regards, Nikolay |
New:
I would like to have a possibility to set/change the default execution node (currently: *master*) of Jenkins pipeline jobs. It is not about the node used for the execution of the Jenkinsfile. It is about the node where the job execution starts. This is because we are using Jenkins with many different teams and I would like to prevent any job executions on the master node. The job is always trying to start on the master node. Why? !screenshot-1.png|thumbnail! UPDATE: Over the [NodeLabel Parameter Plugin|https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin] (as job parameter) I was able to change this behavior, but it would be very nice if there will be another way to change it! I will be very happy to receive any help or feedback about this feature. Best regards, Nikolay |
Nikolay Nachev
made changes -
| Component/s | Original: workflow-cps-global-lib-plugin [ 21714 ] |
Nikolay Nachev
made changes -
| Component/s | New: workflow-job-plugin [ 21716 ] |