[JIRA] [workflow-plugin] (JENKINS-32552) Multibranch project git branch checkout
Title: Message Title
Jean Detoeuf created an issue
Jenkins / JENKINS-32552
Multibranch project git branch checkout
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
21/Jan/16 2:25 PM
Priority:
Minor
Reporter:
Jean Detoeuf
Currently, in a multibranch workflow job, git scm checks out in detached mode and not on $ {env.BRANCH_NAME}. My script generates files based on git info, which is why I added those lines after "checkout scm" : {{sh "git branch -D ${env.BRANCH_NAME}
|| echo 1" sh "git checkout -b $ {env.BRANCH_NAME}
"}}
Is there a way to make this a default ? Is there a reason why this is not done like this ?
Add Comment
[JIRA] [workflow-plugin] (JENKINS-27695) Allocate node waiting for executor
Jean Detoeuf created JENKINS-27695 Allocate node waiting for executor Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 01/Apr/15 9:06 AM Description: I updated jenkins from 1.606 to 1.607. Since then, workflow builds hang on "allocating node". Running: Allocate node : Start Still waiting to schedule task Waiting for next available executor System logs are as follows : Timer task hudson.model.Queue$MaintainTask@6f7ff478 failed java.lang.NullPointerException at java.util.concurrent.ConcurrentSkipListMap.comparable(ConcurrentSkipListMap.java:617) at java.util.concurrent.ConcurrentSkipListMap.doGet(ConcurrentSkipListMap.java:786) at java.util.concurrent.ConcurrentSkipListMap.get(ConcurrentSkipListMap.java:1640) at jenkins.model.Nodes.getNode(Nodes.java:216) at jenkins.model.Jenkins.getNode(Jenkins.java:1667) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getLastBuiltOn(ExecutorStepExecution.java:187) at hudson.model.queue.MappingWorksheet$WorkChunk.init(MappingWorksheet.java:202) at hudson.model.queue.MappingWorksheet$WorkChunk.init(MappingWorksheet.java:172) at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:390) at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:318) at hudson.model.Queue.maintain(Queue.java:1355) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2435) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) This build was functional before upgrading Jenkins. Environment: 1.607 Project: Jenkins Priority: Blocker Reporter: Jean Detoeuf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-27695) Allocate node waiting for executor
Jean Detoeuf commented on JENKINS-27695 Allocate node waiting for executor I downgraded to 1.606 and the build works correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-user-vars-plugin] (JENKINS-26953) Support for workflow-plugin
Jean Detoeuf created JENKINS-26953 Support for workflow-plugin Issue Type: Improvement Assignee: Jesse Glick Components: build-user-vars-plugin, workflow-plugin Created: 13/Feb/15 9:02 AM Description: The user build vars plugin is not available for a workflow job. This plugin should either be made available to workflow jobs or the variables could be directly generated in the workflow plugin, just as the job parameters are made available as variables inside workflow jobs. Environment: 1.598 workflow-plugin 1.2 user-build-vars-plugin 1.4 Project: Jenkins Labels: workflow-plugin build-user-vars-plugin Priority: Minor Reporter: Jean Detoeuf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24550) When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Jean Detoeuf
commented on JENKINS-24550
When I update my Jenkins from 1.563 to 1.566 or later，my Internet Explorer gets warning：Your Internet Explorer appears to be set to a non-defalut Document Mode
One quick workaround is to use IP address instead of DNS name. In my case, DNS name is marked as intranet site and intranet site are required to show in compatibility modes as a group policy. Refering to IP address instead of DNS name solved the issue, although there could be a better way.
Searched a bit on the subject. File layout.jelly contains meta http-equiv="X-UA-Compatible" content="IE=Edge"/ which should override compatibility mode in some cases. I also tried adding the following before html tag
j:if test="${isMSIE}"
st:setHeader name="X-UA-Compatible" value="IE=Edge" /
/j:if
as Microsoft recommended adding a header with the same values to enforce view policy before page rendering (cf http://msdn.microsoft.com/en-us/library/ff955275%28v=vs.85%29.aspx)
Hope this helps
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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.
