[JIRA] (JENKINS-56657) Can not build jenkinsfile-runner with JDK 11
Title: Message Title
Thomas Collignon created an issue
Jenkins / JENKINS-56657
Can not build jenkinsfile-runner with JDK 11
Issue Type:
Bug
Assignee:
Unassigned
Components:
jenkinsfile-runner
Created:
2019-03-21 10:43
Environment:
MacOsX
Priority:
Minor
Reporter:
Thomas Collignon
Hi Like I said in https://github.com/jenkinsci/ci.jenkins.io-runner/issues/67, I cannot build jenkinsfile-runner with Java 11.0.1 (it works perfectly with Java 1.8.0_172) I got this trace : {{[INFO] [INFO] Reactor Summary: [INFO] [INFO] Jenkinsfile Runner 256.0-1.0-beta-7-544bc7e2959c47649a74b0dad69f12df154aa1b6-SNAPSHOT SUCCESS [ 6.617 s] [INFO] bootstrap .. FAILURE [ 2.208 s] [INFO] setup .. SKIPPED [INFO] payload-dependencies ... SKIPPED [INFO] payload SKIPPED [INFO] jenkinsfile-runner . SKIPPED [INFO] tests 256.0-1.0-beta-7-544bc7e2959c47649a74b0dad69f12df154aa1b6-SNAPSHOT SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 11.284 s [INFO] Finished at: 2019-03-21T11:10:06+01:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) on project bootstrap: Compilation failure: Compilation failure: [ERROR]
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-33226) Add options to configure runtime constraints on resources (memory, cpu)
Title: Message Title Thomas Collignon commented on JENKINS-33226 Re: Add options to configure runtime constraints on resources (memory, cpu) PR is here for memory and cpu : https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/45 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-33226) Add options to configure runtime constraints on resources (memory, cpu)
Title: Message Title Thomas Collignon updated an issue Jenkins / JENKINS-33226 Add options to configure runtime constraints on resources (memory, cpu) Change By: Thomas Collignon Environment: Jenkins ver. 1.625.3.1 Plugin Version: 1.6.5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-33226) Add options to configure runtime constraints on resources (memory, cpu)
Title: Message Title Thomas Collignon created an issue Jenkins / JENKINS-33226 Add options to configure runtime constraints on resources (memory, cpu) Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 29/Feb/16 9:17 PM Priority: Minor Reporter: Thomas Collignon If we use the docker-custom-build-environment-plugin with swarm, we maybe want to add runtime constraints to container in order to manager the clusters. Typically if we can add options to set memory and cpu limit it will be great Add Comment
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32542) Maven project failed with "Connection refused" when built in a docker Container
Title: Message Title Thomas Collignon commented on JENKINS-32542 Re: Maven project failed with "Connection refused" when built in a docker Container No the jenkins slave is "classic". Jenkins master (Linux RHEL) => jenkins slave (another Linux RHEL) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon commented on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Now with the new release 1.6.5 you don't have to set $ {WORKSPACE}
, just Dockerfile like you do at the beginning is good.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project doesn't work with Slave
Title: Message Title Thomas Collignon commented on JENKINS-32861 Re: Checking Dockerfile in project doesn't work with Slave Seem to be good in 1.6.5 for us. You can close this issue if you want. Thanks you for your quick release Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project doesn't work with Slave
Title: Message Title Thomas Collignon commented on JENKINS-32861 Re: Checking Dockerfile in project doesn't work with Slave cool, TY Nicolas, I will test this in my case to check if it's good Your fix is better , I wait for a new channel "Quoi de neuf jenkins", with some tips to write plugin ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project doesn't work with Slave
Title: Message Title Thomas Collignon updated an issue Jenkins / JENKINS-32861 Checking Dockerfile in project doesn't work with Slave Change By: Thomas Collignon Summary: Checking Dockerfile in project is too early in the process doesn't work with Slave Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title Thomas Collignon commented on JENKINS-32758 Re: Docker build from Dockerfile requires full path to Dockerfile Oh I don't know that, maybe Nicolas has an other view? Maybe this could be added in the comment on the field Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon edited a comment on JENKINS-32861 Re: Checking Dockerfile in project is too early in the process I have run more test on this issue, and I think it's appear only on Slave.The test "Your project is missing a Dockerfile", is effective on Master. So if we have slaves, it fail all the times.I will propose a fix in a PR on github : https://github . com/jenkinsci/docker-custom-build-environment-plugin/pull/42 In this state, It's a regression if the plugin is released in 1.6.5. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon commented on JENKINS-32861 Re: Checking Dockerfile in project is too early in the process I have run more test on this issue, and I think it's appear only on Slave. The test "Your project is missing a Dockerfile", is effective on Master. So if we have slaves, it fail all the times. I will propose a fix in a PR on github. In this state, It's a regression if the plugin is released in 1.6.5. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon updated an issue Jenkins / JENKINS-32861 Checking Dockerfile in project is too early in the process Change By: Thomas Collignon In docker-custom-build-environnment-plugin 1.6.5-SNAPSHOT, I have this issue : *Your project is missing a Dockerfile*But I haven' in 1.6.4 release version.In fact this is due to this PR : https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/37I have tested without, and it's works.I think that the test is too early in the process, maybe only with slave? Or only with gerrit-trigger-plugin? Or maybe the control will not be the same at this place? I will continue my test and maybe propose a new PR to fix this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon commented on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,
We set Dockerfile filed to : $ {WORKSPACE}
/Dockerfile, and it's works.
Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile filed field to : ${WORKSPACE}/Dockerfile, and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile field to : _ {code:java} ${WORKSPACE}/ Dockerfile_ Dockerfile {code} and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile field to : _ ${WORKSPACE}/ Dockerfile Dockerfile_ , and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile field to : _ ${WORKSPACE}/Dockerfile_ , and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon created an issue Jenkins / JENKINS-32861 Checking Dockerfile in project is too early in the process Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 09/Feb/16 5:50 PM Environment: Linux master, Linux Slave, Jenkins 1.625.3.1, docker-custom-build 1.6.5-SNAPSHOT, gerrit-trigger-plugin 2.18.3 Labels: plugin regression Priority: Minor Reporter: Thomas Collignon In docker-custom-build-environnment-plugin 1.6.5-SNAPSHOT, I have this issue : Your project is missing a Dockerfile But I haven' in 1.6.4 release version. In fact this is due to this PR : https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/37 I have tested without, and it's works. I think that the test is too early in the process, maybe only with slave? Or only with gerrit-trigger-plugin? I will continue my test and
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon updated an issue Jenkins / JENKINS-32861 Checking Dockerfile in project is too early in the process Change By: Thomas Collignon Environment: Linux master , Linux Slave , Jenkins 1.625.3.1 , docker-custom-build 1.6.5-SNAPSHOT , gerrit-trigger-plugin 2.18.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32393) PATH and HOME are being overwritten when executing command
Title: Message Title Thomas Collignon commented on JENKINS-32393 Re: PATH and HOME are being overwritten when executing command Hi, I have started a PR to fix this : https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/40 I think it's just a beginning, but you can try it, and give your feelings. Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Thomas Collignon commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves This may be a good thing, why not I ask myself if it's possible when asynch mode is on post-build, to get error et bring back to jenkins job trace. In this case the boolean "asynchronously" is necessary I Think to let people chosing the strategy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Thomas Collignon commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves ok I see you work on another plugin to clean periodically or you think added this features in this one? you need some help? right now you think add option "asynchronously" is not necessary ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Thomas Collignon commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Ok I agree with you. So I wait for your new implementation Thank for your answer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Thomas Collignon commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves And I have submit a pull request to add a new option to switch between synch and asynch mode without downgrading : https://github.com/jenkinsci/ws-cleanup-plugin/pull/26 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Thomas Collignon commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves In fact if you want to switch "asynch/synch" mode, you can add Patterns, because this will affect cleanup method : Add Patterns : synch mode No Patterns : asynch mode This is just a trick to see the cleanup problem without downgrade to 0.23. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
