[JIRA] [core] (JENKINS-20967) Cloud provisioning called when Jenkins is quieting Down

2015-09-29 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow commented on  JENKINS-20967 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud provisioning called when Jenkins is quieting Down  
 
 
 
 
 
 
 
 
 
 
For anyone interested. I had started work on straightening out countBuildable* but a conflicting change made mine unmergable. I don't have the time to look into this in the near future, but my work is still at https://github.com/thomassuckow/jenkins/commits/feature/fix-stuck-queue 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tasks-plugin] (JENKINS-30289) Tasks plugin exception

2015-09-03 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30289 
 
 
 
  Tasks plugin exception  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ulli Hafner 
 
 
 

Components:
 

 tasks-plugin 
 
 
 

Created:
 

 03/Sep/15 9:04 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Thomas Suckow 
 
 
 
 
 
 
 
 
 
 
Task scanner plugin 4.45 Static Analysis 1.43 

 

[TASKS] Found 130 files to scan for tasks
Found 3 open tasks.
java.io.IOException: Remote call on channel failed
	at hudson.remoting.Channel.call(Channel.java:786)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
	at com.sun.proxy.$Proxy5.execute(Unknown Source)
	at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:207)
	at hudson.plugins.analysis.core.HealthAwareReporter.registerResultsOnMaster(HealthAwareReporter.java:361)
	at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:352)
	at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634)
	at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:615)
	at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:308)
	at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108)
	at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131)
	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
	at 

[JIRA] [core] (JENKINS-28704) [Regression] Ball on build in progress does not open console

2015-06-02 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28704 
 
 
 
  [Regression] Ball on build in progress does not open console  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 

URL:
 
 https://github.com/jenkinsci/jenkins/pull/1727 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28704) [Regression] Ball on build in progress does not open console

2015-06-02 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow started work on  JENKINS-28704 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 

Status:
 
 Open InProgress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28425) UI: Build history overflows

2015-06-02 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow resolved as Fixed 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
Regression documented at JENKINS-28704 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28425 
 
 
 
  UI: Build history overflows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28704) [Regression] Ball on build in progress does not open console

2015-06-02 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28704 
 
 
 
  [Regression] Ball on build in progress does not open console  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Thomas Suckow 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 02/Jun/15 11:13 PM 
 
 
 

Labels:
 

 core css build-history 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Thomas Suckow 
 
 
 
 
 
 
 
 
 
 
JENKINS-28425 created a regression where the ball on an build in progress does not open the console. 
The selectors never should have been grouped together even though the spacing should be the same. 
Fix: 

 

.build-row-cell .pane.build-name .display-name {
margin-left: 20px;
}

.build-row-cell .indent-multiline {
padding-left: 20px !important;  /* Sync changes with func expandControlsTo50Percent in hudson-behavior.js */
}
 

 
 
 
 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-28425) UI: Build history overflows

2015-06-02 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow commented on  JENKINS-28425 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: UI: Build history overflows  
 
 
 
 
 
 
 
 
 
 
I missed the effect it had on the ball link. This is probably also why the console link broke the last time. These two selectors never should have been grouped. 
A better fix would be: 

 

.build-row-cell .pane.build-name .display-name {
margin-left: 20px;
}

.build-row-cell .indent-multiline {
padding-left: 20px !important;  /* Sync changes with func expandControlsTo50Percent in hudson-behavior.js */
}
 

 
I don't have time to make a PR at the moment. If someone could do that it would be appreciated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name

2015-05-27 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow edited a comment on  JENKINS-28506 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name  
 
 
 
 
 
 
 
 
 
 Iinstalledthe plugin developmentbuild ,theprojectthathasa/inthebranchnamehasn'tcommittedinafewdays.SoIdidsomeroundabouttestsbecauseitisn'teasytomakeatemporarygitrepoinmyenvironmenteither.Thepollinglogslookgood:{code}StartedonMay27,20158:11:00AMUsingstrategy:Default[poll]LastBuiltRevision:Revisionabcdef(refs/remotes/origin/feature/foo)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh://server/git/project.git#timeout=10[poll]Latestremoteheadrevisiononrefs/heads/feature/foois:abcdef-alreadybuiltby212Done.Took0.77secNochanges{code}{code}StartedonMay27,20158:30:58AMUsingstrategy:Default[poll]LastBuiltRevision:Revisionfecba(origin/master)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh://server/git/project.git#timeout=10[poll]Latestremoteheadrevisiononrefs/heads/feature/foois:abcdefDone.Took0.85secChangesfound{code}AlsoseemsthatJENKINS-27332isresolved(andprobablyhasbeenforawhile) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-24687) Broken job list if build name is extended

2015-05-27 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow edited a comment on  JENKINS-24687 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Broken job list if build name is extended  
 
 
 
 
 
 
 
 
 
 Alright.Sothisisn'trelatedtoanythingIchangedandIdon'thavetimetofixitandIcan'tjustifytomyworkthatIshouldfindtime.Thatsaid,Ididtakeapeekatit.Foranyonewhowantstolookatit,somethinglikethefollowingcouldwork.{code}a.model-link.inside{text-overflow:ellipsis;width:100%;white-space:nowrap;overflow:hidden;max-width:100px;display:inline-block;}{code}Butithassideeffectsandpotentialsideeffects:#Itshrinkstheprogressbarinsomecases#Youcannotreadtheentirenamebecauseitisnolongerwrappedandshowsellipses#Thepartyoucanreadistheleastsignificantpart(liketheyear).(MaybefixablewithmoreCSSbutthatmaylookweird,soyoucouldaddmoremarkupandevenmorecsstotryandcompensate)#Onthejobpage,youreallyonlyhave9charactersofspacetoworkwith(ellipsestakeuptwoofthose) !ScreenShot2015-05-27at9.04.54AM.png|thumbnail!!ScreenShot2015-05-27at9.05.05AM.png|thumbnail! Someoneelsecanconsidertheseissues.Idon'tagreewithmakingthebuildnamelong.Pleasedon'treassigntome. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-24687) Broken job list if build name is extended

2015-05-27 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-24687 
 
 
 
  Broken job list if build name is extended  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 

Assignee:
 
 ThomasSuckow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name

2015-05-27 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow commented on  JENKINS-28506 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name  
 
 
 
 
 
 
 
 
 
 
I installed the plugin, the project that has a / in the branch name hasn't committed in a few days. So I did some roundabout tests because it isn't easy to make a temporary git repo in my environment either. 
The polling logs look good: 

 

Started on May 27, 2015 8:11:00 AM
Using strategy: Default
[poll] Last Built Revision: Revision abcdef (refs/remotes/origin/feature/foo)
using GIT_SSH to set credentials Git Credentials
  git --version # timeout=10
  git ls-remote -h ssh://server/git/project.git # timeout=10
[poll] Latest remote head revision on refs/heads/feature/foo is: abcdef - already built by 212
Done. Took 0.77 sec
No changes
 

 

 

Started on May 27, 2015 8:30:58 AM
Using strategy: Default
[poll] Last Built Revision: Revision fecba (origin/master)
using GIT_SSH to set credentials Git Credentials
  git --version # timeout=10
  git ls-remote -h ssh://server/git/project.git # timeout=10
[poll] Latest remote head revision on refs/heads/feature/foo is: abcdef
Done. Took 0.85 sec
Changes found
 

 
Also seems that JENKINS-27332 is resolved (and probably has been for a while) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-24687) Broken job list if build name is extended

2015-05-27 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-24687 
 
 
 
  Broken job list if build name is extended  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 

Attachment:
 
 ScreenShot2015-05-27at9.04.54AM.png 
 
 
 

Attachment:
 
 ScreenShot2015-05-27at9.05.05AM.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-24687) Broken job list if build name is extended

2015-05-27 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow commented on  JENKINS-24687 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Broken job list if build name is extended  
 
 
 
 
 
 
 
 
 
 
Alright. So this isn't related to anything I changed and I don't have time to fix it and I can't justify to my work that I should find time. That said, I did take a peek at it. 
For anyone who wants to look at it, something like the following could work. 

 

a.model-link.inside {
text-overflow: ellipsis;
width: 100%;
white-space: nowrap;
overflow: hidden;
max-width: 100px;
display: inline-block;
}
 

 
But it has side effects and potential side effects: 
 

It shrinks the progress bar in some cases
 

You cannot read the entire name because it is no longer wrapped and shows ellipses
 

The part you can read is the least significant part (like the year). (May be fixable with more CSS but that may look weird, so you could add more markup and even more css to try and compensate)
 

On the job page, you really only have 9 characters of space to work with (ellipses take up two of those)
 
 
Someone else can consider these issues. I don't agree with making the build name long. Please don't reassign to me. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
   

[JIRA] [git-plugin] (JENKINS-27332) git-plugin no longer detects changes of branch with /

2015-05-27 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow commented on  JENKINS-27332 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: git-plugin no longer detects changes of branch with /  
 
 
 
 
 
 
 
 
 
 
JENKINS-28506 has a regression in 2.3.5 that breaks /refs/heads/foo/bar syntax. I believe foo/bar should also work. 
Nicolas, this issue should probably be marked resolved. Do you agree? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-24687) Broken job list if build name is extended

2015-05-26 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow commented on  JENKINS-24687 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Broken job list if build name is extended  
 
 
 
 
 
 
 
 
 
 


JENKINS-28425
 is actually in 1.615, the changelog is wrong. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28425) UI: Build history overflows

2015-05-26 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow commented on  JENKINS-28425 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: UI: Build history overflows  
 
 
 
 
 
 
 
 
 
 
Changelog is wrong: https://github.com/jenkinsci/jenkins/pull/1719 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28425) UI: Build history overflows

2015-05-26 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28425 
 
 
 
  UI: Build history overflows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 

Assignee:
 
 ThomasSuckow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling

2015-05-20 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28506 
 
 
 
  [REGRESSION] Git fails to trigger from polling  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 20/May/15 5:34 PM 
 
 
 

Environment:
 

 Git-Plugin: 2.3.5 
 
 
 

Labels:
 

 git polling pollscm regression 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Thomas Suckow 
 
 
 
 
 
 
 
 
 
 
Expected: ``` [poll] Last Built Revision: Revision abcdef1234 (refs/remotes/origin/feature/myfeature) using GIT_SSH to set credentials Git Credentials  git --version # timeout=10  git ls-remote -h ssh://we16705.pnl.gov/git/watchmen.git refs/heads/feature/myfeature # timeout=10 [poll] Latest remote head revision is: defabc4321 Done. Took 1.8 sec Changes found ``` 
Actual: ``` [poll] Last Built Revision: Revision abcdef1234 (refs/remotes/origin/feature/myfeature) using GIT_SSH to set credentials Git Credentials  git --version # timeout=10  git ls-remote -h ssh://we16705.pnl.gov/git/watchmen.git # timeout=10 Done. Took 1.8 sec ``` 
Workaround: Downgrade to 

[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling

2015-05-20 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28506 
 
 
 
  [REGRESSION] Git fails to trigger from polling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 
 
 
 
 
 
 
 Expected: ``` {code} [poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh:// we16705.pnl.gov server /git/ watchmen project .gitrefs/heads/feature/myfeature#timeout=10[poll]Latestremoteheadrevisionis:defabc4321Done.Took1.8secChangesfound ``` {code} Actual: ``` {code} [poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh:// we16705.pnl.gov server /git/ watchmen project .git#timeout=10Done.Took1.8sec ``` {code} Workaround:DowngradetoGit-Plugin2.3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling

2015-05-20 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28506 
 
 
 
  [REGRESSION] Git fails to trigger from polling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 
 
 
 
 
 
 
 Pollingdoesnotworkwhenthespecifiedbranchisoftheformrefs/heads/feature/myfeature Expected:{code}[poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh://server/git/project.gitrefs/heads/feature/myfeature#timeout=10[poll]Latestremoteheadrevisionis:defabc4321Done.Took1.8secChangesfound{code}Actual:{code}[poll]LastBuiltRevision:Revisionabcdef1234(refs/remotes/origin/feature/myfeature)usingGIT_SSHtosetcredentialsGitCredentialsgit--version#timeout=10gitls-remote-hssh://server/git/project.git#timeout=10Done.Took1.8sec{code}Workaround:DowngradetoGit-Plugin2.3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28425) UI: Build history overflows

2015-05-15 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28425 
 
 
 
  UI: Build history overflows  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Thomas Suckow 
 
 
 

Attachments:
 

 Screen Shot 2015-05-15 at 8.18.35 AM.png, Screen Shot 2015-05-15 at 8.44.59 AM.png 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 15/May/15 3:47 PM 
 
 
 

Labels:
 

 ui build-history 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Thomas Suckow 
 
 
 
 
 
 
 
 
 
 
When there are items such as build parameters or build size they overflow out of the build history panel. 
In addition, when building the circle overlaps with the vertical line. 
 
 
 
 
 
 
 
 
 
 
 
 

  

[JIRA] [core] (JENKINS-28425) UI: Build history overflows

2015-05-15 Thread thomas.suc...@pnnl.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Suckow assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28425 
 
 
 
  UI: Build history overflows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Suckow 
 
 
 

URL:
 
 https://github.com/jenkinsci/jenkins/pull/1705 
 
 
 

Assignee:
 
 ThomasSuckow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-27332) git-plugin no longer detects changes of branch with /

2015-03-10 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 created  JENKINS-27332


git-plugin no longer detects changes of branch with /















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-plugin



Created:


10/Mar/15 11:36 PM



Description:


git-plugin does not detect changes and thus does not trigger builds

Git plugin used to detect changes when the specified branch was "feature/abc" but no longer does.

Does not detect:

Started on Mar 10, 2015 4:13:00 PM
Using strategy: Default
poll Last Built Revision: Revision 5...9 (refs/remotes/origin/feature/abc)
using GIT_SSH to set credentials Git Credentials
  git --version # timeout=10
  git ls-remote -h ssh://myserver/myproject.git # timeout=10
Done. Took 0.81 sec
No changes

Does detect:

Started on Mar 10, 2015 4:16:00 PM
Using strategy: Default
poll Last Built Revision: Revision 1...e (origin/develop)
  git --version # timeout=10
  git ls-remote -h ssh://myserver/otherproject.git # timeout=10
poll Latest remote head revision on origin/develop is: 1...e - already built by 81
Done. Took 0.8 sec
No changes




Workaround:
Revert to GIT Plugin 2.3.4




Environment:


Jenkins 1.601

GIT client plugin 1.16.1

GIT plugin 2.3.5




Project:


Jenkins



Priority:


Major



Reporter:


Thomas Suckow

























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-20967) Cloud provisioning called when Jenkins is quieting Down

2015-02-25 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 commented on  JENKINS-20967


Cloud provisioning called when Jenkins is quieting Down















Changing NodeProvisioner would create a deadlock situation with NonBlockingTasks, such as a Matrix Build. Their slaves may never get created. I think it would be more appropriate to modify the behaviour of countBuildable*() in Queue to only count tasks that are not blocked by shutdown.

I have another pull request manipulating countBuildable, I may make a pull request for this after that one gets accepted.



























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-27034) BuildableItems (Subtasks) are miscounted in the queue

2015-02-23 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 updated  JENKINS-27034


BuildableItems (Subtasks) are miscounted in the queue
















Upping to Major because I have to rebuild Jenkins for each update and I don't really have the time to keep doing that for every update.





Change By:


Thomas Suckow
(23/Feb/15 3:45 PM)




Priority:


Minor
Major



























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-26601) StackOverflow Maven Job Parse Poms

2015-02-23 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 commented on  JENKINS-26601


StackOverflow Maven Job Parse Poms















I no longer see stack overflow in 1.599



























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-27034) BuildableItems (Subtasks) are miscounted in the queue

2015-02-19 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 updated  JENKINS-27034


BuildableItems (Subtasks) are miscounted in the queue
















Change By:


Thomas Suckow
(19/Feb/15 4:10 PM)




Environment:


Jenkins1.598



























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-27034) BuildableItems (Subtasks) are miscounted in the queue

2015-02-19 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 created  JENKINS-27034


BuildableItems (Subtasks) are miscounted in the queue















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


19/Feb/15 4:10 PM



Description:


BuildableItems (Subtasks) are miscounted in the queue

Expected:
When a labeled job is in the queue its nodeprovisioner should report excess load and provision a new node. The "free roaming" nodeprovisioner should report no load and not provision a new node.

Actual:
In addition to JENKINS-25207 (The free roaming nodeprovisioner spawns nodes even though the job is labeled), it is possible for the appropriate nodeprovisioner to not report load because of use of == on the label.

Technical:
Labels are compared in a number of places with == instead of equals

Additionally af55e5345628d31f49390e11a473079bed750fd9, modified the behaviour of the "free roaming" label in the queue. This results in spawning nodes for "free roaming" jobs, even when none exist.

I have included a pull request that resolves these issues.




Project:


Jenkins



Labels:


queue
label
loadstatistics
starvation
nodeprovisioner




Priority:


Minor



Reporter:


Thomas Suckow

























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-25207) NodeProvisioner: multiple instances spawned if Cloud is not EXCLUSIVE

2015-02-10 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 commented on  JENKINS-25207


NodeProvisioner: multiple instances spawned if Cloud is not EXCLUSIVE















I believe https://github.com/jenkinsci/jenkins/pull/1569 should fix the issue you describe



























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] [git-client-plugin] (JENKINS-26026) Submodules gives java.lang.UnsupportedOperationException with jGit

2014-12-11 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 created  JENKINS-26026


Submodules gives java.lang.UnsupportedOperationException with jGit















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-client-plugin



Created:


11/Dec/14 6:43 PM



Description:


When submodules are enabled with jGit building gives:

FATAL: not implemented yet
java.lang.UnsupportedOperationException: not implemented yet
	at org.jenkinsci.plugins.gitclient.JGitAPIImpl.setupSubmoduleUrls(JGitAPIImpl.java:2125)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:622)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:326)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)
	at ..remote call to b4531083cc3f@we13196(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel.call(Channel.java:752)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179)
	at com.sun.proxy.$Proxy100.setupSubmoduleUrls(Unknown Source)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl.setupSubmoduleUrls(RemoteGitImpl.java:477)
	at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:82)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1006)
	at hudson.scm.SCM.checkout(SCM.java:484)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1265)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
	at hudson.model.Run.execute(Run.java:1759)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)




Environment:


Jenkins: 1.592

GIT client plugin: 1.12.0

GIT plugin: 2.3.1




Project:


Jenkins



Labels:


jgit
submodules




Priority:


Minor



Reporter:


Thomas Suckow

























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 

[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with ERROR: Failed to parse POMs java.net.SocketException: Connection reset

2014-02-06 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 commented on  JENKINS-21541


After I upgrade to 1.547, Maven Build fails with ERROR: Failed to parse POMs java.net.SocketException: Connection reset















I've seen this a few times lately, even after 1.549.
It always seems to resolve itself if I restart Jenkins.

Workaround:
1. Click "Manage Jenkins"
2. Click "Manage Plugins"
3. Click "Download now and install after restart"
4. Check the "Restart Jenkins ..." box



























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/groups/opt_out.


[JIRA] (JENKINS-12492) Manage SSH keys for Git in web GUI

2013-01-29 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 commented on  JENKINS-12492


Manage SSH keys for Git in web GUI















Unfortunately the ssh agent plugin happens after scm checkout. I tried to mod the plugin to do it before, but the scm step does not take an environment. I am not experienced with Jenkins plugin dev and gave up at that point.



























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/groups/opt_out.




[JIRA] (JENKINS-14002) Make the git plugin support login credentials

2013-01-07 Thread thomas.suc...@pnnl.gov (JIRA)














































Thomas Suckow
 updated  JENKINS-14002


Make the git plugin support login credentials
















Change By:


Thomas Suckow
(08/Jan/13 12:00 AM)




Summary:


Makethegit
pluing
plugin
supportlogincredentials



























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