[JIRA] [authentication-tokens-plugin] (JENKINS-29370) Add ability to filter TokenSources by external conditions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29370 Re: Add ability to filter TokenSources by external conditions Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/authentication/tokens/api/AuthenticationTokenContext.java src/main/java/jenkins/authentication/tokens/api/AuthenticationTokenSource.java src/main/java/jenkins/authentication/tokens/api/AuthenticationTokens.java src/test/java/jenkins/authentication/tokens/api/AuthenticationTokenContextTest.java http://jenkins-ci.org/commit/authentication-tokens-plugin/4e5848a765d2d19c2059aac8147a74dfd28ce80e Log: JENKINS-29370 Add the concept of an authentication token context Filtering token sources (as originally requested in JENKINS-29370) in the consumer of this API is against the spirit of the API. The consumer should not be required to know which token sources are valid and which are not valid. If it knew which token sources were valid it would just use them directly. The point of this API is to enable the consumer to specify the context within which they want to use the token and then have the credentials (of a type unknown to the consumer) be converted (by a converter of a type unknown to the consumer) into a token (of a type known to the consumer) 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] [subversion-plugin] (JENKINS-26458) E155021: This client is too old to work with the working copy
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Telmah, you can avoid it if you use jsvn (cross-platform). Here you have an example: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.5/version configuration tagBasehttp://hostname/scm/svn/project/tags/tagBase autoVersionSubmodulestrue/autoVersionSubmodules releaseProfilesrelease/releaseProfiles arguments-Dmaven.test.skip -Denv=vm/arguments goalsdeploy/goals providerImplementations svnjavasvn/svn /providerImplementations /configuration dependencies dependency groupIdcom.google.code.maven-scm-provider-svnjava/groupId artifactIdmaven-scm-provider-svnjava/artifactId version2.1.1/version /dependency /dependencies /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] [mstest-plugin] (JENKINS-29316) MSTEST : inconclusive tests are reported as 'failed' instead of 'skipped'
Title: Message Title Ivo Bellin Salarin commented on JENKINS-29316 Re: MSTEST : inconclusive tests are reported as 'failed' instead of 'skipped' Alexandre, would you please send me an example TRX, in order to add it to the unit test material? 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-29376) Label expression help is missing in recent Jenkins versions
Title: Message Title Oliver Gondža started work on JENKINS-29376 Change By: Oliver Gondža 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] [p4-plugin] (JENKINS-29296) P4 Plugin: Downstream job not using correct changelist
Title: Message Title Paul Allen commented on JENKINS-29296 Re: P4 Plugin: Downstream job not using correct changelist Glad to hear this has resolved your issue. The 'change' param is used by the 'Perforce Swarm' review integration and is read at the start of the build. I added P4_CHANGELIST early on in development, to help downstream Jobs and labels, but it is not read at the start of a build. I don't know where CHANGELIST is set perhaps another 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] [project-inheritance-plugin] (JENKINS-29061) Unable to configure or reconfigure a new inheritance project....
Title: Message Title Alexandru Prian commented on JENKINS-29061 Re: Unable to configure or reconfigure a new inheritance project Had the same problem. As a workaround you can do the following: Change Mange Jenkins - Configure Global Security - Markup Formatter to Raw HTML or Safe HTML Came to this thanks to https://github.com/i-m-c/jenkins-inheritance-plugin/issues/19 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] [mstest-plugin] (JENKINS-23531) MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed
Title: Message Title Ivo Bellin Salarin closed an issue as Won't Fix Have a look at the previous comment, about the output of the unit test and the valididty of the attached XML. Jenkins / JENKINS-23531 MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed Change By: Ivo Bellin Salarin Status: Open Closed Resolution: Won'tFix 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jess Recena Soto updated an issue Jenkins / JENKINS-29293 Repositories set as external are not triggered if they are in the list of jobs after the main repository Change By: Manuel Jess Recena Soto *Subversionschema:* 1. # We'veamainreponamedforexampleappcore 2. # Thisrepositoryhasatotalof9repositoriessetasexternals 3. # 8from9repositoryarefromthesamerootrepositorynamedappcore-toolswhichhavethefollowingstructure: ## appcore-tools/library/main/trunk ## appcore-tools/library/local/trunk ## appcore-tools/library/book/trunk ## ... 4. # Thelastexternalpointtoadifferentrepository 5. # AllthesereposareonthesamesvnserverandtheuserusedtocheckoutthesourceshasRWaccesstoall.*Jenkinsjobsschema:* 1. # IhaveajobcalledAppcore-BuildStablewhichisresponsiblethebuildthemainrepositoryappcore/trunk. 2. # Foreachexternalfrompoint2,we'veseparatejobstobuildthem.ThenameconventionisAppcore-Main-BuildStable,Appcore-Local-BuildStable,Appcore-Book-BuildStable,etc.. 3. # Thelastexternalfromthedifferentrepositorydoesn'thaveajob(thecodeisnotchangedthere).AlljobshavethePoolSCMoptionenabledandSVNtriggerhasthepostcommithookenabled.*Behaviour:*AfterI'veupdatedJenkinsandSubversionplugintothelatestversions,thepoolingisnotworkinganymoreforallthejobsthatareafterAppcore-BuildStableinthelistofjobs(whicharealphabeticallyordered).IfIcommitsomethingonappcore-tools/library/book/trunk,thejobAppcore-Book-BuildStablestarts.IfIcommitsomethingonappcore-tools/library/main/trunk,thejobAppcore-Main-BuildStabledoesn'tstartbecauseisaftertheAppcore-BuildStable.IfIchangethejobnamefromAppcore-Main-BuildStabletoAppcore-BA-Main-BuildStableandIcommitsomethingontherepo,thejobstarts.TheworkaroundformewastorenamethejobAppcore-BuildStabletoAppcore-X-BuildStable.Inthisway,alltheotherjobsarebeforethisjob. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-29323) Problem with launching AutoCAD inside Jenkins using AutoCAD API
Title: Message Title Volodymyr Hnatiuk commented on JENKINS-29323 Re: Problem with launching AutoCAD inside Jenkins using AutoCAD API Yes, I set up my Jenkins to running from the my user account and AutoCAD launched from a my user account too. 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] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Title: Message Title Russell Gallop commented on JENKINS-25111 Re: Ability to Copy Artifacts from a Phase Job This patch also works for me for a simple 1 phase multijob (tried revision 17c94362f0111b12b7dea7d1a9728666f9949a39) and provides a very neat solution to the problem of triggering multiple jobs and gathering results. Is there a plan to release a new version of the plugin with this functionality soon? 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-29376) Label expression help is missing in recent Jenkins versions
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-29376 Label _expression_ help is missing in recent Jenkins versions Change By: Oliver Gondža Labels: lts-candidate 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Title: Message Title Pere Orga commented on JENKINS-23232 Re: SEVERE: I/O error in channel Chunked connection I got rid of this by enabling the TCP port for JNLP slave agents 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] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Sam Gleske commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth Yep, the over a year old quote was a copy/paste error from house cleaning really old issues. I will actually re-open this since it is less than a year old. I'd appreciate it if someone could provide details on how to reproduce the above error. 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-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-25791 User.impersonate throws ClassCastException when using GitHub auth Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [junit-plugin] (JENKINS-29383) Failure summary does not work when special chars are present in path
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-29383 Failure summary does not work when special chars are present in path Issue Type: Bug Assignee: Oliver Gondža Components: junit-plugin Created: 13/Jul/15 11:06 AM Priority: Minor Reporter: Oliver Gondža When there are special chars (`|`, ``, `#`, etc) present in the path, clicking + have no effect. This can happen on matrix test report page in case axes/values contain any such characters. The same will likely happen when present in test case/method name. The relative path to the test report is used as html element ID fragments. These IDs are passed unescaped into _javascript_ handler so it is looking up the unescaped variants. Add Comment
[JIRA] [subversion-plugin] (JENKINS-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Subversion Plugin doesn't support all the subversion operations so it's not always possible to avoid using subversion CLI. For me this problem happens when subversion CLI is version 1.7 so I cannot SVN version from 1.7 to 1.8 in the Jenkins configuration because then the subversion CLI client doesn't work. 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] [websphere-deployer-plugin] (JENKINS-29384) Support deployment to Liberty apps directory
Title: Message Title Julie MacNaught created an issue Jenkins / JENKINS-29384 Support deployment to Liberty apps directory Issue Type: Improvement Assignee: Unassigned Components: websphere-deployer-plugin Created: 13/Jul/15 12:02 PM Labels: configuration Priority: Critical Reporter: Julie MacNaught Deploying war files to the dropins directory is not sufficient for applications that need to specify security roles in server.xml. I know I will have to edit server.xml to add these other elements, but I will only have to do it once. I'm hoping to use the websphere-deployer-plugin to update applications (CI) running on a remote Liberty instance. I considered fixing it myself, but I can't seem to get the plugin to build. It's missing a number of dependencies: [ERROR] Failed to execute goal on project websphere-deployer: Could not resolve dependencies for project org.jenkins-ci.plugins:websphere-deployer:hpi:1.3-SNAPSHOT: The following artifacts could not be resolved: com.ibm.ws:admin:jar:8.5.0, com.ibm.ws:orb:jar:8.5.0, com.ibm.ws:liberty-connector:jar:8.5.5, com.ibm.ws:liberty-rest-connector:jar:8.5.5, com.ibm.ws:liberty-basic:jar:8.5.5, com.ibm.ws:liberty-endpoint:jar:8.5.5,
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Sam Gleske commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth rsandell could you provide a means to reproduce the error? 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] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Daniel Wagner commented on JENKINS-28517 Re: [MSTEST] XML coverage report file not found I've to finish my sample project to create sample data but didn't find the time yet. 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] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure (Praqma case 13083)
Title: Message Title Bue Petersen resolved as Fixed Jenkins / JENKINS-28640 Quotationmarks in commit message leads to merge failure (Praqma case 13083) Change By: Bue Petersen Status: Open 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-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Daniel Beck edited a comment on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth [~sag47]'Fixed'hasaspecificmeaningthatdoesnotappeartoapplyhere(ifitwasactuallyfixed,thisshouldbeaDuplicatepointingtothefixedissue).'CannotReproduce'or'Incomplete'wouldprobablybestindicatethestatusofthis. BTW,thisisuseisn'tevenayearold. 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] [authentication-tokens-plugin] (JENKINS-29370) Add ability to filter TokenSources by external conditions
Title: Message Title
stephenconnolly edited a comment on JENKINS-29370
Re: Add ability to filter TokenSources by external conditions
InmyviewfilteringtokensourcesintheconsumerofthisAPIisagainstthespiritoftheAPI.Theconsumershouldnotberequiredtoknowwhichtokensourcesarevalidandwhicharenotvalid.Ifit new knew whichtokensourceswerevaliditwouldjustusethemdirectly.ThepointofthisAPIistoenabletheconsumertospecifythecontextwithinwhichtheywanttousethetokenandthenhavethecredentials(ofatypeunknowntotheconsumer)beconverted(byaconverterofatypeunknowntotheconsumer)intoatoken(ofatypeknowntotheconsumer)Sotherootusecasehereissomethinglikethis:1.AsaconsumerIamgoingtoauthenticatea{{XYZHttpConnection}}usingDigestauthentication,pleasegivemeamatcherforcredentialsthatcanbeusedinthiscontext...nowpleaseconvertthisspecificcredentialintothe{{XYZHttpAuthenticator}}instanceInthe1.1versionoftheauthenticationtokensAPIweassumethattherewouldbeseparateclassesfora{{BasicXYZHttpAuthenticator}}anda{{DigestXYZHttpAuthenticator}},butthatisanarrogantassumptiontomake.Weshouldnotbeassuminganythingofthelibrarywearemappingto.Inotherwords,inthecontextofthisexamplethelibraryshouldbefreetohaveonandonlyone{{XYZHttpAuthenticator}}classthatperhapsgasa{{getScheme()}}methodtodifferentiatebetweenbasicanddigestauthentication.Sotherealsolutionforthisissueistoallowamorefinegrainedspecificationofthecontextwithinwhichwewillusethetoken.Thusinsteadofsayingwewanta{{XYZHttpAuthenticator}}token,weshouldbesayingwewanta{{XYZHttpAuthenticator}}tokenforthepurposeofdigestauthentication
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] [authentication-tokens-plugin] (JENKINS-29370) Add ability to filter TokenSources by external conditions
Title: Message Title stephenconnolly commented on JENKINS-29370 Re: Add ability to filter TokenSources by external conditions In my view filtering token sources in the consumer of this API is against the spirit of the API. The consumer should not be required to know which token sources are valid and which are not valid. If it new which token sources were valid it would just use them directly. The point of this API is to enable the consumer to specify the context within which they want to use the token and then have the credentials (of a type unknown to the consumer) be converted (by a converter of a type unknown to the consumer) into a token (of a type known to the consumer) So the root use case here is something like this: 1. As a consumer I am going to authenticate a XYZHttpConnection using Digest authentication, please give me a matcher for credentials that can be used in this context... now please convert this specific credential into the XYZHttpAuthenticator instance In the 1.1 version of the authentication tokens API we assume that there would be separate classes for a BasicXYZHttpAuthenticator and a DigestXYZHttpAuthenticator, but that is an arrogant assumption to make. We should not be assuming anything of the library we are mapping to. In other words, in the context of this example the library should be free to have on and only one XYZHttpAuthenticator class that perhaps gas a getScheme() method to differentiate between basic and digest authentication. So the real solution for this issue is to allow a more fine grained specification of the context within which we will use the token. Thus instead of saying we want a XYZHttpAuthenticator token, we should be saying we want a XYZHttpAuthenticator token for the purpose of digest authentication Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are
[JIRA] [weblogic-deployer-plugin] (JENKINS-26992) WebLogic deployer does not expand variables
Title: Message Title
Jurek Malinowski reopened an issue
I think it still doesn't work as expected (weblogic-deployer-plugin-3.2). If I set base directory to $ {WORKSPACE}\build\dist I'll get error during deployment that the base directory specified ${WORKSPACE}
\build\dist is invalid. I looked at plugin's code and such string doesn't match pattern ENV_VAR_PATTERN at ParameterValueResolver class. Maybe it would be better to use in FreeStyleJobArtifactSelectorImpl instead of:
String resolvedBaseDirectory = ParameterValueResolver.resolveEnvVar(baseDirectory, VarUtils.getEnvVars(build, listener));
something like: EnvVars vars = build.getEnvironment(listener); String resolvedBaseDirectory = vars.expand(baseDirectory);
Jenkins / JENKINS-26992
WebLogic deployer does not expand variables
Change By:
Jurek Malinowski
Resolution:
Fixed
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [p4-plugin] (JENKINS-29296) P4 Plugin: Downstream job not using correct changelist
Title: Message Title Paul Allen resolved as Fixed Use the 'change' param to set the change and P4_CHANGELIST to evaluate the change used in the build. Note: their values may not be the same. For example, take a code line //depot/projA/src/... with changes: change 196 'Fix A' change 198 'Fix B' change 204 'Feature X' Setting 'change' to 200 will build from that change, but the last submitted change under the code line might be 198, so P4_CHANGELIST will report 198. Jenkins / JENKINS-29296 P4 Plugin: Downstream job not using correct changelist Change By: Paul Allen Status: Open 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
[JIRA] [jobconfighistory-plugin] (JENKINS-24630) Exception when opening JobConfigurationHistory that have changed operation
Title: Message Title Pere Orga commented on JENKINS-24630 Re: Exception when opening JobConfigurationHistory that have changed operation Its weird that dependencies can be disabled and dependant modules can still be enabled. FWIW plugin is [Maven Project Plugin](https://wiki.jenkins-ci.org/display/JENKINS/Maven+Project+Plugin) (Plugin ID: maven-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] [mstest-plugin] (JENKINS-23531) MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed
Title: Message Title Ivo Bellin Salarin commented on JENKINS-23531 Re: MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed vishal Mane, the file you've attached is not valid XML. Try one of the xml validators you can find online, or your favourite xml editor. Everyone will tell you the same message: The line DEBUG: S: LPUSH pubsub:LogQHotelBeds \Y\0 �\0\0\0\0\0\0�g��ܶ%��J�?Xo�~i��s�RKǀі contains an invalid XML character entity. Which one? The sequence. This means that your unit test outputs the given sequence. MSTest just copies it in the TRX. Without any further validation. In order to fix the mstest behavior, in the past I've patched the mstest plugin in order to skip invalid characters. I've skipped the ones explicitly listed in the official XML specification. Your character sequence doesn't appear in the official XML specification. Microsoft is aware of the problem (Jitin John, which reported an update on 4/9/2015 is from Microsoft). I'm not aware of a fix concerning vstest.console or mstest. Let's hope it will be included in VS2015 (which will be released on 07/20/2015). As a conclusion, you can do one of the following things: 1) modify your unit tests from printing invalid xml character entities on StdOut or on the Debug trace. 2) contact Microsoft in order to ask them to fix the problem in mstest and vstest.console. 3) modify the code in ContentCorrector.java in order to add the given character sequence to the list of the invalid ones (and propose a pull request by means of the github interface). Have a good day, Ivo 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
[JIRA] [subversion-plugin] (JENKINS-26458) E155021: This client is too old to work with the working copy
Title: Message Title Telmah commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Another example of this problem - when on host machine 1.7.x version of client are installed. Regardless of configuration settings (mine is set to 1.7) Jenkins are using 1.8 client workspaces. Maven uses host installed client (1.7.x in my case) So after checking out project using Jenskins subversion (via job workflow) Maven cannot correctly operate with workspace using host client and rises an error 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-29385) JenkinsUrl doesn't work properly
Title: Message Title David Perez created an issue Jenkins / JENKINS-29385 JenkinsUrl doesn't work properly Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Jul/15 12:44 PM Environment: Apache redirect https (without rewriting protocol) to jenkins(http). Labels: jenkins url configuration Priority: Trivial Reporter: David Perez I am using Jenkins over HTTPS/SSL. I can navigate to https://jenkins.mydomain.com without any problems. All links are correct with https:// in front of them. I can properly navigate through almost all Jenkins pages Except when Jenkins tries to redirect (e.g after login, after clicking Build, etc). Whenever Jenkins tries to redirect to any page, it sends me to http:// page (not httpS://) In the Code I've seen many calls to FormApply.success, that doesnot use JenkinsUrl. and they send a relative path to stapler framework. Acording to the StaplerResponse implementation, it completes the URL with (unwanted) request information (line
[JIRA] [pretested-integration-plugin] (JENKINS-28590) Author of last commit becomes the author of the integration commit (Praqma case 13102)
Title: Message Title Bue Petersen resolved as Fixed Jenkins / JENKINS-28590 Author of last commit becomes the author of the integration commit (Praqma case 13102) Change By: Bue Petersen Status: Open 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] [pretested-integration-plugin] (JENKINS-28596) Hardcoded branch name when resolving commit messages (Praqma case 13073)
Title: Message Title Bue Petersen resolved as Fixed Jenkins / JENKINS-28596 Hardcoded branch name when resolving commit messages (Praqma case 13073) Change By: Bue Petersen Status: Open 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-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Daniel Beck commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth Sam Gleske 'Fixed' has a specific meaning that does not appear to apply here (if it was actually fixed, this should be a Duplicate pointing to the fixed issue). 'Cannot Reproduce' or 'Incomplete' would probably best indicate the status of 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] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Title: Message Title Bue Petersen resolved as Fixed Jenkins / JENKINS-29369 Accumulated commit message is locale and launguage dependent (Praqma case 13296) Change By: Bue Petersen Status: Open 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] [junit-plugin] (JENKINS-6087) please separate JUnit plugin functionality from the core into a separate plugin
Title: Message Title Oliver Gondža resolved as Fixed Jenkins / JENKINS-6087 please separate JUnit plugin functionality from the core into a separate plugin Change By: Oliver Gondža Status: Open 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-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Sam Gleske commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth Daniel Beck I'll have to go through most of the issues I closed and change their status. I closed them with the 'Fixed' status which was, as you say, likely an inappropriate status. It's too bad there isn't a 'Stale' status. As none of the statuses seemed to apply. Cannot Reproduce might be the closest appropriate status because the issue is so old I can't reproduce it (or am not willing due to the age) without knowing the specific versions of software being used. 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] [ldap-plugin] (JENKINS-29382) LDAP authentication doesn't work with ADAM
Title: Message Title Flix Belzunce Arcos created an issue Jenkins / JENKINS-29382 LDAP authentication doesn't work with ADAM Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ldap-plugin, plugin-proposals Created: 13/Jul/15 10:51 AM Priority: Minor Reporter: Flix Belzunce Arcos ADAM is an LDAP directory service. The way Jenkins does authentication in LDAP is bind as the administrator DN and search for the User. bind as the user DN found in step 1 Get the users DN details The LDAP authentication process implemented by Jenkins, is not compatible with every Active Directory configuration in which Jenkins Users have not “Readers” role.
[JIRA] [subversion-plugin] (JENKINS-26458) E155021: This client is too old to work with the working copy
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Slawomir Czarko, What operation are you trying to do? I would like to get a step by step process to reproduce your problem. 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] [nunit-plugin] (JENKINS-28144) content of NUnit file is not shown correct inside browser
Title: Message Title Norbert Krimbacher updated an issue Jenkins / JENKINS-28144 content of NUnit file is not shown correct inside browser sorry for my delayed answer... Change By: Norbert Krimbacher Attachment: NUnitconfiguration.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-29336) loadStatistics API not accessible
Title: Message Title Stefan Bisplinghoff commented on JENKINS-29336 Re: loadStatistics API not accessible Try …/loadStatistics/api/xml?depth=2. This works, thank you! However, I hoped/expected to find the actual (integer) number of idle/busy executors with the API functions. Even after some hours of completely idle master, the number just converged to the real value: loadStatistics availableExecutors hour history3.9296637/history history3.9218485/history history3.913165/history ... latest3.9296637/latest /hour ... /availableExecutors ... /loadStatistics Where did you get the 404 producing URL from? Intuitively, I tried /computer/…/load-statistics/api as with any other URL 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Ricardo Garca Fernndez, I assume that this functionality was working in prior versions, Isn't that so? 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-commons-plugin] (JENKINS-28657) Support creation of named fingerprints in DockerFingerprints
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28657 Re: Support creation of named fingerprints in DockerFingerprints Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/commons/fingerprint/DockerFingerprints.java http://jenkins-ci.org/commit/docker-commons-plugin/ae64ac19f227739fc79682cb63f7cebb3510aadf Log: Merge pull request #37 from oleg-nenashev/named-fingerprints [FIXED JENKINS-28657] - Support the creation of named fingerprints Compare: https://github.com/jenkinsci/docker-commons-plugin/compare/e09ead383aa6...ae64ac19f227 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-commons-plugin] (JENKINS-28657) Support creation of named fingerprints in DockerFingerprints
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28657 Support creation of named fingerprints in DockerFingerprints Change By: SCM/JIRA link daemon Status: InProgress 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] [docker-commons-plugin] (JENKINS-28657) Support creation of named fingerprints in DockerFingerprints
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28657 Re: Support creation of named fingerprints in DockerFingerprints Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/commons/fingerprint/DockerFingerprints.java http://jenkins-ci.org/commit/docker-commons-plugin/39b57e715d83ffeb3f8bfe0378538f45e44d58b2 Log: [FIXED JENKINS-28657] - Support the creation of named fingerprints The fix also changes the default behavior for missing names. Instead of non-informative docker-image we will be using Docker image $(64-char id) (which may be too long BTW) 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] [collabnet-plugin] (JENKINS-29314) Improving teamforge-collabnet plugin.
Title: Message Title JCAT assigned an issue to JCAT Jenkins / JENKINS-29314 Improving teamforge-collabnet plugin. Change By: JCAT Assignee: whsu JCAT 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] [github-oauth-plugin] (JENKINS-17916) NullPointerException when GitHub OAuth Plugin is used
Title: Message Title Sam Gleske closed an issue as Cannot Reproduce Jenkins / JENKINS-17916 NullPointerException when GitHub OAuth Plugin is used Change By: Sam Gleske Status: Reopened Closed Resolution: CannotReproduce 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] [github-oauth-plugin] (JENKINS-21895) Latest LTS causes swarm clients fail to authenticate when using github-oauth
Title: Message Title Sam Gleske commented on JENKINS-21895 Re: Latest LTS causes swarm clients fail to authenticate when using github-oauth I'm closing this as duplicate and linked to the duplicate issue. Feel free to follow progress in that issue. 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] [github-oauth-plugin] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Title: Message Title Sam Gleske edited a comment on JENKINS-24383 Re: Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin Fixedin Pleasetry release0.21. 1. Feelfreetore-openifyouexperienceotherwise. 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Ricardo Garca Fernndez commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Manuel Jess Recena Soto, yes because of that we realise of this bug after updating svn 2.4.5 to svn 2.5 (2.5.1) 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] [github-oauth-plugin] (JENKINS-15765) IRC Bot does not take commands
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-15765 IRC Bot does not take commands Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-14777) Broken links to static resources
Title: Message Title Sam Gleske closed an issue as Cannot Reproduce Jenkins / JENKINS-14777 Broken links to static resources Change By: Sam Gleske Status: Open Closed Resolution: CannotReproduce 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] [github-oauth-plugin] (JENKINS-15765) IRC Bot does not take commands
Title: Message Title Sam Gleske closed an issue as Cannot Reproduce Jenkins / JENKINS-15765 IRC Bot does not take commands Change By: Sam Gleske Status: Reopened Closed Resolution: CannotReproduce 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] [github-oauth-plugin] (JENKINS-16347) No images served to Anonymous users
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-16347 No images served to Anonymous users Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-16347) No images served to Anonymous users
Title: Message Title Sam Gleske closed an issue as Cannot Reproduce Jenkins / JENKINS-16347 No images served to Anonymous users Change By: Sam Gleske Status: Reopened Closed Resolution: CannotReproduce 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] [github-oauth-plugin] (JENKINS-17916) NullPointerException when GitHub OAuth Plugin is used
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-17916 NullPointerException when GitHub OAuth Plugin is used Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [mstestrunner-plugin] (JENKINS-29389) Categories option does not allow quotation marks around single value
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-29389 Categories option does not allow quotation marks around single value Issue Type: Bug Assignee: Unassigned Components: mstestrunner-plugin Created: 13/Jul/15 2:42 PM Environment: Windows Server 2012 Priority: Trivial Reporter: Nikolas Falco Following MSTest Command Line in MSDN specifics that single categories do not have to enclose in quotation marks, they are needed only for more than one category (aggregated with at least logical operator ! | ) Add Comment
[JIRA] [p4-plugin] (JENKINS-29386) Add workflow-plugin support for Post-build actions
Title: Message Title Paul TBBle Hampson created an issue Jenkins / JENKINS-29386 Add workflow-plugin support for Post-build actions Issue Type: Improvement Assignee: Unassigned Attachments: 0001-Untested-implementation-of-SimpleBuildStep-for-the-N.patch Components: p4-plugin Created: 13/Jul/15 1:17 PM Environment: Jenkins 1.618 Workflow 1.8 P4 Plugin 1.2.4 Labels: workflow Priority: Minor Reporter: Paul TBBle Hampson It'd be really handy if the two Notifiers, AssetNotifier and TagNotifier implemented SimpleBuildStep and so were available for use in Workflow scripts. According to Plugin Developer Guide it should be as simple as implementing
[JIRA] [collabnet-plugin] (JENKINS-29314) Improving teamforge-collabnet plugin.
Title: Message Title JCAT assigned an issue to whsu Jenkins / JENKINS-29314 Improving teamforge-collabnet plugin. Change By: JCAT Assignee: JCAT whsu 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] [github-oauth-plugin] (JENKINS-13354) Jenkins very slow when not an admin
Title: Message Title Sam Gleske commented on JENKINS-13354 Re: Jenkins very slow when not an admin This is fixed in release 0.21. https://github.com/jenkinsci/github-oauth-plugin/pull/27 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] [github-oauth-plugin] (JENKINS-14777) Broken links to static resources
Title: Message Title Sam Gleske updated JENKINS-14777 Jenkins / JENKINS-14777 Broken links to static resources Change By: Sam Gleske Status: Reopened Open 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] [github-oauth-plugin] (JENKINS-14777) Broken links to static resources
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-14777 Broken links to static resources Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-24010 github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Change By: Sam Gleske Resolution: Fixed Status: Closed Reopened 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] [github-oauth-plugin] (JENKINS-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Title: Message Title Sam Gleske closed an issue as Duplicate Jenkins / JENKINS-24010 github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Change By: Sam Gleske Status: Reopened Closed Resolution: Duplicate 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] [github-oauth-plugin] (JENKINS-25809) Issue when using embeddable-build-status
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-25809 Issue when using embeddable-build-status Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-20883) Can't publish arbitrary URLs
Title: Message Title Sam Gleske edited a comment on JENKINS-20883 Re: Can't publish arbitrary URLs Thisissuewasresolvedwithrelease0.21. 1. https://github.com/jenkinsci/github-oauth-plugin/pull/29 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] [cmakebuilder-plugin] (JENKINS-29329) Visual Studio/MSBuild projects can not be built implicitly anymore
Title: Message Title Lars Bilke commented on JENKINS-29329 Re: Visual Studio/MSBuild projects can not be built implicitly anymore In my cache there is no `CMAKE_MAKE_PROGRAM` entry too. If I understand the [CMake docs](http://www.cmake.org/cmake/help/v3.2/variable/CMAKE_MAKE_PROGRAM.html) correctly for `MSBuild` there is no `CMAKE_MAKE_PROGRAM` entry in the cache: he Visual Studio generators set this to the full path to MSBuild.exe... These generators prefer to lookup the build tool at build time rather than to store CMAKE_MAKE_PROGRAM in the CMake cache ahead of time. This is because the tools are version-specific and can be located using the Windows Registry. 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] [cmakebuilder-plugin] (JENKINS-29329) Visual Studio/MSBuild projects can not be built implicitly anymore
Title: Message Title
Lars Bilke edited a comment on JENKINS-29329
Re: Visual Studio/MSBuild projects can not be built implicitly anymore
Inmycachethereisno`CMAKE_MAKE_PROGRAM`entrytoo.IfIunderstandthe [ CMakedocs ]( [ http://www.cmake.org/cmake/help/v3.2/variable/CMAKE_MAKE_PROGRAM.html ) ] correctlyfor`MSBuild`thereisno`CMAKE_MAKE_PROGRAM`entryinthecache:{quote} he The VisualStudiogeneratorssetthistothefullpathtoMSBuild.exe...ThesegeneratorsprefertolookupthebuildtoolatbuildtimeratherthantostoreCMAKE_MAKE_PROGRAMintheCMakecacheaheadoftime.Thisisbecausethetoolsareversion-specificandcanbelocatedusingtheWindowsRegistry.{quote}
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] [github-oauth-plugin] (JENKINS-20883) Can't publish arbitrary URLs
Title: Message Title Sam Gleske commented on JENKINS-20883 Re: Can't publish arbitrary URLs Additionally one can make use of a matrix-based authorization strategy. GitHub users are surfaced as Jenkins users. GitHub teams and groups are surfaced as Jenkins Groups. It is documented in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Github+OAuth+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] [github-oauth-plugin] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-27045 Cannot use jenkins-cli with github oauth plugin Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [deploy-websphere-plugin] (JENKINS-29392) Unable to install EAR through websphere-plugin in Remote WebSphere v8.5.5
Title: Message Title Ansuman Swain created an issue Jenkins / JENKINS-29392 Unable to install EAR through websphere-plugin in Remote WebSphere v8.5.5 Issue Type: Bug Assignee: asanso Components: deploy-websphere-plugin, websphere-deployer-plugin Created: 13/Jul/15 3:00 PM Environment: org.jenkins-ci.main:jenkins-war:1.609.1 (Installed in windows) WebSphere v8.5.5 (remote Red Hat) Java Version - 1.7JDK Labels: jenkins plugin Priority: Critical Reporter: Ansuman Swain The test connection i successful to the remote websphere through SOAP port. The application is in the location /app/WebApps/MyAppEAR/ location in the remote unix server. The node/cell/server details are provided as required.While installing the application only uninstallation of ear is successful. The EAR file from the location /app/WebApps/MyAppEAR/ is getting deleted.However no installation of EAR after that. The console output is also not showing any error. Below is the output for reference.
[JIRA] [junit-plugin] (JENKINS-29383) Failure summary does not work when special chars are present in path
Title: Message Title Oliver Gondža started work on JENKINS-29383 Change By: Oliver Gondža 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] [robot-plugin] (JENKINS-29353) Configurable number of builds for trends generation
Title: Message Title Nickolay Rumyantsev commented on JENKINS-29353 Re: Configurable number of builds for trends generation I've created a pull request for this feature: https://github.com/jenkinsci/robot-plugin/pull/10 Although it might be a bit straightforward, please take a look and make your suggestions. 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] [github-oauth-plugin] (JENKINS-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-24010 github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Title: Message Title Sam Gleske closed an issue as Fixed Jenkins / JENKINS-24010 github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Change By: Sam Gleske Status: Reopened Closed 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] [github-oauth-plugin] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-24383 Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Title: Message Title Sam Gleske closed an issue as Cannot Reproduce Jenkins / JENKINS-24383 Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin Change By: Sam Gleske Status: Reopened Closed Resolution: CannotReproduce 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] [mstestrunner-plugin] (JENKINS-29391) Add support to GLOB Ant pattern in test files
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-29391 Add support to GLOB Ant pattern in test files Issue Type: Improvement Assignee: Unassigned Components: mstestrunner-plugin Created: 13/Jul/15 2:53 PM Environment: Windows 2012 Jenkins 1.596.2 Priority: Major Reporter: Nikolas Falco Add support to GLOB Ant pattern in test files. Actually patterns must identify exactly each articafct that come from build process with a full/relative to workspace path. The only workaround is a build step that collect all test container to an enviroment variable and use it in test files field of the following mstestrunner step. Add Comment
[JIRA] [github-oauth-plugin] (JENKINS-25459) Authorization by Github Commiter strategy broken.
Title: Message Title Sam Gleske closed an issue as Duplicate Jenkins / JENKINS-25459 Authorization by Github Commiter strategy broken. Change By: Sam Gleske Status: Reopened Closed Resolution: Duplicate 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] [github-oauth-plugin] (JENKINS-25459) Authorization by Github Commiter strategy broken.
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-25459 Authorization by Github Commiter strategy broken. Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Sam Gleske closed an issue as Cannot Reproduce Jenkins / JENKINS-27045 Cannot use jenkins-cli with github oauth plugin Change By: Sam Gleske Status: Reopened Closed Resolution: CannotReproduce 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-29390) Parameterization for Docker Container configuration.
Title: Message Title Stefan Kahlhfer created an issue Jenkins / JENKINS-29390 Parameterization for Docker Container configuration. Issue Type: New Feature Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 13/Jul/15 2:44 PM Priority: Major Reporter: Stefan Kahlhfer The Docker Custom Build Environment Plugin runs Docker Containers with a bunch of configuration parameters which seem to be hardcoded or discovered automatically from the slave's environment. This leads to errors on running containers. Resp. it requires the Docker image to be built especially for those configurations which on the other hand would make it less portable and therefor breaks one of the most important advantages of Docker. For example: Jenkins slave is running as user Jenkins on the Docker host those User-ID is 1001. To avoid permission errors we have to configure a user with ID 1001 in the image/container as well. What if we use this image on a Docker host where the Jenkins user has ID 1002? The PATH environment variable on the host is set to /usr/local/bin:/usr/bin. In the container which emulates another Distro it should also list /bin. The container has to run a service in the background (e.g. Xvfb to perform UI
[JIRA] [ssh-agent-plugin] (JENKINS-28689) Make compatible with Workflow plugin
Title: Message Title Manuel Jess Recena Soto commented on JENKINS-28689 Re: Make compatible with Workflow plugin This plugin will require Jenkins baseline 1.599 because SimpleBuildWrapper was introduced in this version. 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] [proc-cleaner-plugin] (JENKINS-29388) Make PsCleanerTest.doNotCleanOnSlaveWithOtherBuildRunning() portable
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-29388 Make PsCleanerTest.doNotCleanOnSlaveWithOtherBuildRunning() portable Issue Type: Improvement Assignee: Unassigned Components: proc-cleaner-plugin Created: 13/Jul/15 1:56 PM Priority: Minor Reporter: Pavel Janoušek This test uses shell's CLI 'sleep' command which isn't portable on all platforms. We can use portable approach from JENKINS-29195 for execution of long running task instead of 'sleep' here. Add Comment
[JIRA] [github-oauth-plugin] (JENKINS-21895) Latest LTS causes swarm clients fail to authenticate when using github-oauth
Title: Message Title Sam Gleske reopened an issue Jenkins / JENKINS-21895 Latest LTS causes swarm clients fail to authenticate when using github-oauth Change By: Sam Gleske Resolution: Fixed Status: Resolved Reopened 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] [github-oauth-plugin] (JENKINS-21895) Latest LTS causes swarm clients fail to authenticate when using github-oauth
Title: Message Title Sam Gleske closed an issue as Duplicate Jenkins / JENKINS-21895 Latest LTS causes swarm clients fail to authenticate when using github-oauth Change By: Sam Gleske Status: Reopened Closed Resolution: Duplicate 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] [p4-plugin] (JENKINS-29387) Cannot sync into workspaces with '@' in their path
Title: Message Title
Paul TBBle Hampson created an issue
Jenkins / JENKINS-29387
Cannot sync into workspaces with '@' in their path
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
13/Jul/15 1:29 PM
Environment:
Jenkins 1.618 Workflow 1.8 P4 Plugin 1.2.4
Labels:
workflow
Priority:
Major
Reporter:
Paul TBBle Hampson
Attempting to sync into a workspace that contains '@' in the path fails:
p4 client -i
Error in client specification. Embedded special characters (*, %%, #, @) not allowed in 'd:\jenkins\workspace\workflow_test_parallel@2'.
This is particularly an issue for workflow-plugin as it tends to append '@' to workspace paths such as the path used by the 'Store DSL script in SCM' ('@script'), and the second and later workspaces for a particular build script on a
[JIRA] [github-oauth-plugin] (JENKINS-20883) Can't publish arbitrary URLs
Title: Message Title Sam Gleske commented on JENKINS-20883 Re: Can't publish arbitrary URLs This issue was resolved with release 0.21. https://github.com/jenkinsci/github-oauth-plugin/pull/29 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] [github-oauth-plugin] (JENKINS-25809) Issue when using embeddable-build-status
Title: Message Title Sam Gleske closed an issue as Duplicate Jenkins / JENKINS-25809 Issue when using embeddable-build-status Change By: Sam Gleske Status: Reopened Closed Resolution: Duplicate 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] [nunit-plugin] (JENKINS-28144) content of NUnit file is not shown correct inside browser
Title: Message Title Norbert Krimbacher commented on JENKINS-28144 Re: content of NUnit file is not shown correct inside browser it's rather a simple configuration, the result file is located in the workspace root folder of the Jenkins project 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] [warnings-plugin] (JENKINS-29203) StyleCop warnings are counted twice
Title: Message Title Michael Fowler commented on JENKINS-29203 Re: StyleCop warnings are counted twice All of the StyleCop error #'s begin with SA. They should be easy to separate. We would like them separate so that we can treat the MSBuild warnings with greater severity (possibly fail the build). 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] [email-ext-plugin] (JENKINS-29325) Excluded Recipients Receive Notifications
Title: Message Title Alex Earl commented on JENKINS-29325 Re: Excluded Recipients Receive Notifications Sorry if I wasn't clear, I would like to see the config.xml for the job that is running. 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] [cli] (JENKINS-29400) Cannot connect to Jenkins CLI with https
Title: Message Title Tommy Romano created an issue Jenkins / JENKINS-29400 Cannot connect to Jenkins CLI with https Issue Type: Bug Assignee: Unassigned Components: cli Created: 13/Jul/15 6:40 PM Labels: cli ssl https Priority: Minor Reporter: Tommy Romano Our Jenkins server was switched to https from http and now we continue to get issues relating to ssl. Here is the error we keep getting: Exception in thread main java.io.IOException: Failed to connect to https://ncs-jenkins.cisco.com:8443/ at hudson.cli.CLI.getCliTcpPort(CLI.java:266) at hudson.cli.CLI.init(CLI.java:126) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:466) at hudson.cli.CLI.main(CLI.java:382) Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake Any help would be appreciated because I have not found any solutions to this issue yet.
[JIRA] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username
Title: Message Title A C commented on JENKINS-28421 Re: Information provided to email-ext should be perforce email address, not perforce username Upping to Major, as this prevents an important part of continuous integration workflow, namely directly identifying and emailing developers the results of their checkins. 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] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username
Title: Message Title A C assigned an issue to Paul Allen Jenkins / JENKINS-28421 Information provided to email-ext should be perforce email address, not perforce username Change By: A C Assignee: PaulAllen 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] [gradle-jpi-plugin] (JENKINS-29327) classes from junit Jenkins plugin are not available in class path in IDEA
Title: Message Title Alexey Java commented on JENKINS-29327 Re: classes from junit Jenkins plugin are not available in class path in IDEA IDEA guys fixed this bug in IDEA 15. yay! 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] [plugin-usage-plugin] (JENKINS-29401) UI: table is based on no standard Jenkins UI
Title: Message Title Victor Martinez started work on JENKINS-29401 Change By: Victor Martinez 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] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Title: Message Title
Karl Katzke edited a comment on JENKINS-12523
Re: Could not initialize class org.libvirt.Connect
Igetthesameissueas RenKorthaus G.Kr. withPlugin1.8.5,Jenkins1.6.20,andOpenJDK1.7{noformat}javax.servlet.ServletException:java.lang.NoClassDefFoundError:Couldnotinitializeclassorg.libvirt.Connect atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
[JIRA] [warnings-plugin] (JENKINS-29203) StyleCop warnings are counted twice
Title: Message Title Ulli Hafner edited a comment on JENKINS-29203 Re: StyleCop warnings are counted twice Theneithertheregular_expression_needstobeadaptedorinthecreateWarningmethodshouldreturnFALSE_POSITIVEforthesewarnings.Interestedinprovidngapullrequest?Thechangesshouldbestraightforwardto[MsBuildParser|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/MsBuildParser.java]andthe[testcase| https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/java/hudson/plugins/warnings/parser/MsBuildParserTest.java ]. 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] [warnings-plugin] (JENKINS-29203) StyleCop warnings are counted twice
Title: Message Title Ulli Hafner edited a comment on JENKINS-29203 Re: StyleCop warnings are counted twice Theneithertheregular_expression_needstobeadaptedorinthecreateWarningmethodshouldreturnFALSE_POSITIVEforthesewarnings.Interestedinprovidngapullrequest?Thechangesshouldbestraightforwardto [MsBuildParser| https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/MsBuildParser.java ] andthe [ testcase |] . 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] [ssh-agent-plugin] (JENKINS-29062) IncompatibleClassChangeError; AgentServer.safelyClose
Title: Message Title Christopher Miller commented on JENKINS-29062 Re: IncompatibleClassChangeError; AgentServer.safelyClose Update: seems that upgrading the JDK version on the slaves in question to Java 7 fixes this problem. The wiki page for the plugin mentions this, but for whatever reason we haven't hit this problem running java 6 up until today. 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] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username
Title: Message Title A C updated an issue Jenkins / JENKINS-28421 Information provided to email-ext should be perforce email address, not perforce username Change By: A C Priority: Minor Major 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.
