[JIRA] [tap-plugin] (JENKINS-31415) diagnostics lines have whitespaces shrunked
Title: Message Title Andrei Neculau created an issue Jenkins / JENKINS-31415 diagnostics lines have whitespaces shrunked Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 05/Nov/15 10:44 AM Environment: jenkins 1.584, tap-plugin 1.23 Priority: Minor Reporter: Andrei Neculau Diagnostic lines, in the source TAP file, look like not ok 3 foo.lux # FAIL at line 13:34 # expected # ==0== # actual fail pattern matched "==1==" but when checking the TAP results in the Jenkins UI (tap-plugin views), it comes out as # FAIL at line 13:34 # expected # ==0== # actual fail pattern matched "==1==" The same happens with whitespaces after the # sign, which is even worse (think pretty-printed JSON output).
[JIRA] [git-plugin] (JENKINS-29287) Merge build fails when ref contains remote's name
Title: Message Title Andrei Neculau commented on JENKINS-29287 Re: Merge build fails when ref contains remote's name I cannot declare my destination branch as such, since it comes down as a generator parameter. The sender uses origin/master (a value accepted by the git plugin in the SCM block) and cannot be changed. Several other branch formats (accepted by the git plugin in the SCM block) would fail as well: refs/heads/master, remotes/origin/master, refs/remotes/origin/master. 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-29287) Merge build fails when ref contains remote's name
Title: Message Title
Andrei Neculau created an issue
Jenkins / JENKINS-29287
Merge build fails when ref contains remote's name
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-plugin
Created:
08/Jul/15 10:34 AM
Priority:
Blocker
Reporter:
Andrei Neculau
There are a few closed issues mentioning the change in behaviour of the Remote field of the Merge Build section. This is NOT a duplicate of those.
It seems the code is joining the Remote and the Ref(Branch) with a /, but that is incorrect when the ref is origin/trunk (this is recommended when trunk is ambiguous) — the command will become git rev-parse /origin/trunk^ {commit}
.
Add Comment
[JIRA] [git-plugin] (JENKINS-29287) Merge build fails when ref contains remote's name
Title: Message Title Andrei Neculau commented on JENKINS-29287 Re: Merge build fails when ref contains remote's name Mark, I have updated the ticket accordingly (I hope). Thank you 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-29287) Merge build fails when ref contains remote's name
Title: Message Title Andrei Neculau commented on JENKINS-29287 Re: Merge build fails when ref contains remote's name The first comment describes exactly the problem (and a workaround) 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-29287) Merge build fails when ref contains remote's name
Title: Message Title
Andrei Neculau updated an issue
Jenkins / JENKINS-29287
Merge build fails when ref contains remote's name
Change By:
Andrei Neculau
Environment:
Jenkins1.584git-plugin2.3.5
Thereareafewclosedissuesmentioning Iexperience the change sameproblemas in behaviourof JENKINS-21845but the Remotefieldofthe suggestedworkaroundisnotapplicable(becausemybranchrefisveryspecific MergeBuild origin/master section ) . ThisisNOTaduplicateofthose Thefailedcommandlookslikegitrev-parse/origin/master . Addingtheremotenameorigininthemergebuildconfigurationonlyendsuptorunningthecommandlikegitrev-parseorigin/origin/master. ItseemsthecodeisjoiningtheRemoteandtheRef(Branch)witha/,butthatisincorrectwhentherefisorigin/ trunk master (thisisrecommendedwhentrunkisambiguous)---thecommandwillbecomegitrev-parse/origin/ trunk master ^{commit}.
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-29287) Merge build fails when ref contains remote's name
Title: Message Title Andrei Neculau edited a comment on JENKINS-29287 Re: Merge build fails when ref contains remote's name Thefirstcomment inJENKINS-21845 describesexactlytheproblem(andaworkaround whichisnotapplicableforthisissue ) 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] [delivery-pipeline-plugin] (JENKINS-25451) build after other projects
Andrei Neculau created JENKINS-25451 build after other projects Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 05/Nov/14 2:37 PM Description: I have created a job X that "depends" on a job Y in a delivery-pipeline (build) and triggers whenever Y succeeds. At that point, I fetch the PIPELINE_VERSION and use it in the environment. I noticed that job X then starts appearing the in the delivery-pipeline view, which is not correct I think. It is not a subproject, nor a downstream job by my definition. Project: Jenkins Priority: Minor Reporter: Andrei Neculau 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] [cli] (JENKINS-16126) CLI Basic authentiation does not work
Andrei Neculau commented on JENKINS-16126 CLI Basic authentiation does not work i am getting the same with 1.588 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] [cli] (JENKINS-16126) CLI Basic authentiation does not work
Andrei Neculau edited a comment on JENKINS-16126 CLI Basic authentiation does not work I am getting the same with 1.588 NOTE: I am also having a reverse-proxy (nginx, not apache) in front of the jenkins instance 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] [scm-sync-configuration-plugin] (JENKINS-25409) Add manual/scheduled commit for offline changes
Andrei Neculau edited a comment on JENKINS-25409 Add manual/scheduled commit for offline changes Is there a way to do that via a Groovy script? That would be neat for a temporary solution as a manual/scheduled job. 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] [scm-sync-configuration-plugin] (JENKINS-25409) Add manual/scheduled commit for offline changes
Andrei Neculau commented on JENKINS-25409 Add manual/scheduled commit for offline changes Is there a way to do that via a Groovy script? That would be neat for a temporary solution. 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] [scm-sync-configuration-plugin] (JENKINS-25409) Add manual/scheduled commit for offline changes
Andrei Neculau created JENKINS-25409 Add manual/scheduled commit for offline changes Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 03/Nov/14 10:13 AM Description: At times, changes can be made "offline", meaning not via Jenkins itself, but via awk, sed, manual editing, etc. The plugin could allow for 1) a manual sync - although this would be a manual step i.e. can easily be forgotten 2) a scheduled commit - every X minutes, sync all changes 3) sync all changes when calling "reload configuration from disk" Project: Jenkins Labels: plugin configuration Priority: Minor Reporter: Andrei Neculau 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] [scm-sync-configuration-plugin] (JENKINS-25410) Incorrect timestamp in footer status message
Andrei Neculau created JENKINS-25410 Incorrect timestamp in footer status message Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 03/Nov/14 10:15 AM Description: At times, changes can be made "offline", meaning not via Jenkins itself, but via awk, sed, manual editing, etc. The plugin could allow for 1) a manual sync - although this would be a manual step i.e. can easily be forgotten 2) a scheduled commit - every X minutes, sync all changes 3) sync all changes when calling "reload configuration from disk" Project: Jenkins Labels: configuration plugin Priority: Minor Reporter: Andrei Neculau 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] [scm-sync-configuration-plugin] (JENKINS-25410) Incorrect timestamp in footer status message
Andrei Neculau updated JENKINS-25410 Incorrect timestamp in footer status message Change By: Andrei Neculau (03/Nov/14 10:18 AM) Description: Attimes,changescanbemadeoffline,meaningnotviaJenkinsitself,butviaawk,sed,manualediting,etc.Theplugincouldallowfor1)amanualsync - althoughthiswouldbeamanualstepi.e.caneasilybeforgotten2)ascheduledcommit - everyXminutes,syncallchanges3)syncallchangeswhencallingreloadconfigurationfromdisk invalid-- 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] [scm-sync-configuration-plugin] (JENKINS-25410) Incorrect timestamp in footer status message
Andrei Neculau resolved JENKINS-25410 as Not A Defect Incorrect timestamp in footer status message Sorry about this. I filed an invalid ticket. Change By: Andrei Neculau (03/Nov/14 10:17 AM) Status: Open Resolved Resolution: NotADefect 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] [jobgenerator] (JENKINS-24727) Project from build triggers do not get deleted. Only downstream projects do
Andrei Neculau created JENKINS-24727 Project from build triggers do not get deleted. Only downstream projects do Issue Type: Bug Assignee: Unassigned Components: jobgenerator Created: 16/Sep/14 1:47 PM Description: Subprojects (projects started from build triggers) are not deleted. Environment: jobgenerator 1.22 Project: Jenkins Priority: Major Reporter: Andrei Neculau 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-14264) Link to the console output missing in popup when log 200Kb
Andrei Neculau commented on JENKINS-14264 Link to the console output missing in popup when log 200Kb a 2year very-visible bug is still open 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-22641) Jenkins no longer kills running processes after job fails
Andrei Neculau commented on JENKINS-22641 Jenkins no longer kills running processes after job fails I can confirm this issue with 0.558 on a Debian 7.4 and Ubuntu 12.04 with Open/Oracle 6/7 JDKs, on master/slave. And I can also confirm that downgrading to 0.552 solved it (didn't have the time to do a "bisect" on intermediary versions). Thanks for reporting the issue! I thought I'm misunderstanding the processtreekiller feature 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.
