[JIRA] (JENKINS-42014) Query on PTC Integrity plugin
Title: Message Title PTC ALM updated JENKINS-42014 Resolving as not revert from poster Jenkins / JENKINS-42014 Query on PTC Integrity plugin Change By: PTC ALM Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-42014) Query on PTC Integrity plugin
Title: Message Title PTC ALM edited a comment on JENKINS-42014 Re: Query on PTC Integrity plugin Resolving as not no revert from poster Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-42567) si viewproject gets stuck (sometimes) while checking out Integrity project
Title: Message Title PTC ALM updated an issue Jenkins / JENKINS-42567 si viewproject gets stuck (sometimes) while checking out Integrity project Change By: PTC ALM Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-42567) si viewproject gets stuck (sometimes) while checking out Integrity project
Title: Message Title PTC ALM created an issue Jenkins / JENKINS-42567 si viewproject gets stuck (sometimes) while checking out Integrity project Issue Type: Bug Assignee: PTC ALM Components: integrity-plugin Created: 2017/Mar/08 9:51 AM Labels: integrity-plugin Priority: Minor Reporter: PTC ALM si viewproject gets stuck (sometimes) while checking out Integrity project. This is seen in conjunction with pipeline plugin (and also without). Investigation required to reproduce and provide a resolution for this. Add Comment
[JIRA] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title
PTC ALM edited a comment on JENKINS-31739
Re: NPE from IntegritySCM.checkout from Workflow
Fix committed. This snippet should work now from 2.0.3: {code:java} node\{ checkout changelog: false, poll: false, scm: [$class: 'IntegritySCM', checkpointBeforeBuild: false, configPath: '#d:/Sample', configurationName: 'bc1afd06-2e11-4406-8571-3ba109bb05ef', deleteNonMembers: false, fetchChangedWorkspaceFiles: false, restoreTimestamp: false, serverConfig: '87a09dce-feec-49b0-a9c7-db9917d6aa05', skipAuthorInfo: false]} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title
PTC ALM edited a comment on JENKINS-31739
Re: NPE from IntegritySCM.checkout from Workflow
Fix committed. This snippet should work now from 2.0.3:node\{ checkout changelog: false, poll: false, scm: [$class: 'IntegritySCM', checkpointBeforeBuild: false, configPath: '#d:/Sample', configurationName: 'bc1afd06-2e11-4406-8571-3ba109bb05ef', deleteNonMembers: false, fetchChangedWorkspaceFiles: false, restoreTimestamp: false, serverConfig: '87a09dce-feec-49b0-a9c7-db9917d6aa05', skipAuthorInfo: false]}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title
PTC ALM commented on JENKINS-31739
Re: NPE from IntegritySCM.checkout from Workflow
Fix committed. This snippet should work now from 2.0.3: node{ checkout changelog: false, poll: false, scm: $class: 'IntegritySCM', checkpointBeforeBuild: false, configPath: '#d:/Sample', configurationName: 'bc1afd06-2e11-4406-8571-3ba109bb05ef', deleteNonMembers: false, fetchChangedWorkspaceFiles: false, restoreTimestamp: false, serverConfig: '87a09dce-feec-49b0-a9c7-db9917d6aa05', skipAuthorInfo: false }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-42010) Issue with executing PTC-MKS integrity SI commands in jenkins
Title: Message Title PTC ALM commented on JENKINS-42010 Re: Issue with executing PTC-MKS integrity SI commands in jenkins Hi Sudarshan, There is a recent problem posed on the PTC community which is an exact same problem that you're facing. https://www.ptcusercommunity.com/message/479748 You could follow the suggestion given in the thread above and give your problem a try. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42010) Issue with executing PTC-MKS integrity SI commands in jenkins
Title: Message Title
PTC ALM commented on JENKINS-42010
Re: Issue with executing PTC-MKS integrity SI commands in jenkins
Hi Sudarshan, This is a helper method for the actual configureSubproject. Could you show what
MKS.MKSHelper('mkstest-server example','7002')
&
mksHelper.configureSubproject
is doing internally?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-42014) Query on PTC Integrity plugin
Title: Message Title PTC ALM commented on JENKINS-42014 Re: Query on PTC Integrity plugin It should be able to, however we haven't tested this scenario. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42097) PTC integrity plugin creates multiple API Sessions and does not end the session after jenkins job is complete
Title: Message Title PTC ALM commented on JENKINS-42097 Re: PTC integrity plugin creates multiple API Sessions and does not end the session after jenkins job is complete Hi Sudarshan, Yes the default checkout thread count is 5. However, that number is a subset of the API session count, since API session would be required for firing any Integrity command in the plugin (projectinfo, viewproject, checkpoint and others). Getting back to the original issue, how long after the job termination are you still seeing open API sessions and how many? Is there any other activity happening on the Integrity Server that is firing api calls? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42097) PTC integrity plugin creates multiple API Sessions and does not end the session after jenkins job is complete
Title: Message Title PTC ALM commented on JENKINS-42097 Re: PTC integrity plugin creates multiple API Sessions and does not end the session after jenkins job is complete Hi Sudarshan, The plugin kills off the active API sessions once a job is completed. This may take some time depending on the number of active sessions, but it usually doesn't take much time to clean up. How long after the job are these sessions still active? Is there any other integration/activity on the same Integrity Server that is firing api calls? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42010) Issue with executing PTC-MKS integrity SI commands in jenkins
Title: Message Title PTC ALM commented on JENKINS-42010 Re: Issue with executing PTC-MKS integrity SI commands in jenkins Ok. Can you attach the part of the script where it tries to connect to Integrity client? (it usually would be where it fires the first si command) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42014) Query on PTC Integrity plugin
Title: Message Title PTC ALM commented on JENKINS-42014 Re: Query on PTC Integrity plugin Ah ok. I think I see what you are trying to do now. You are pre configuring the subs on a specific checkpoint (assuming on the parent project trunk line) and running the build on the parent project trunk itself and the preconfigured subs should get picked up. If this is the case, it should work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42010) Issue with executing PTC-MKS integrity SI commands in jenkins
Title: Message Title PTC ALM commented on JENKINS-42010 Re: Issue with executing PTC-MKS integrity SI commands in jenkins Hi Sudarshan, I think in the case of running this script as a Windows Batch build step, the user and password (being taken on the default Integrity connection) is different from when you are running it standalone shell/command environment. Can you try running the script with a valid user/password, replacing the user=None, password=None variables in the script? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42010) Issue with executing PTC-MKS integrity SI commands in jenkins
Title: Message Title PTC ALM commented on JENKINS-42010 Re: Issue with executing PTC-MKS integrity SI commands in jenkins Hi Sudarshan, Is the python script running the Integrity commands with a specific user (--user= --password=)? Can you attach the script on this issue so we can have a look? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42014) Query on PTC Integrity plugin
Title: Message Title PTC ALM commented on JENKINS-42014 Re: Query on PTC Integrity plugin Hi Sudarshan, Yes. The plugin would checkout whatever is specified in the project configuration inside the job configuration. If the project configuration is specified as trunk, it would check out trunk. If the project configuration is specified as a dev path (with a #d parameter), it would checkout the dev path, You could also specify a particular checkpoint/project revision (with a #b parameter) to be checked out on the project configuration inside the jenkins job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41838) No progress while executing pipeline checkout jobs. No exception or error
Title: Message Title PTC ALM commented on JENKINS-41838 Re: No progress while executing pipeline checkout jobs. No exception or error Hi Simon, To understand this better, can you send across the jenkins logs (https://wiki.jenkins-ci.org/display/JENKINS/Logging) & the IntegritySCM logs (https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin#PTCIntegrityPlugin-Troubleshooting) for this scenario? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42010) Issue with executing PTC-MKS integrity SI commands in jenkins
Title: Message Title PTC ALM commented on JENKINS-42010 Re: Issue with executing PTC-MKS integrity SI commands in jenkins Hi Sudarshan, Is this seen while running the python script? Or during a build step? What is the exact command that mksHelper.configureSubproject firing? Is it firing with a user having permissions to access Integrity Client directory? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42014) Query on PTC Integrity plugin
Title: Message Title PTC ALM commented on JENKINS-42014 Re: Query on PTC Integrity plugin Hi Sudarshan, I am entirely clear of this use case, but I don't think this would work. ILM plugin works with the Integrity Project specified in the SCM section (I assume you mean the same as SCM path). Even if your external python script reconfigures the sub project to a particular checkpoint, the ILM plugin would not be able to work in the same context as your python script. The plugin works exclusively with the project specified in the plugin configuration and fires si projectinfo and si viewproject on the project path to determine the correct branch to work on. Externally reconfiguring the project using a script wouldn't influence the project path determination of the plugin. It is exclusively driven by the Integrity project configuration path parameter in the plugin. Your use case could result in inconsistent plugin behavior if external scripts could be allowed to manipulate the job's project path during build runtime, since the job project configuration is actually different from intended build output. Maybe you could clarify your use case better, so we can figure out another way? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-42049) How to kill unstoppable zombie pipeline jobs
Title: Message Title PTC ALM commented on JENKINS-42049 Re: How to kill unstoppable zombie pipeline jobs Hi Simon, On the face of it, this looks more like a pipeline problem. Usually pipeline builds should resume an _unsuccessful _ job after a jenkins restart. Is Jenkins restart a frequent scenario for you? How about letting the first pipeline batch just run through after the jenkins restart, instead of trying to abort them? Does the pipeline after restart just gets stuck somewhere? There is infact an open feature request on pipeline for this: https://issues.jenkins-ci.org/browse/JENKINS-33761. Regards, Anurag. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM closed an issue as Won't Fix Closing this issue since this is not a plugin issue. If there are further queries, please raise a new JIRA request Jenkins / JENKINS-37621 Post-Build Checkpoint fail with NoSuchElementException Change By: PTC ALM Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34158) No information about changes displayed
Title: Message Title PTC ALM updated an issue Jenkins / JENKINS-34158 No information about changes displayed Change By: PTC ALM Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41314) Selections of trunk and branches of projects from PTC integrity for build
Title: Message Title PTC ALM closed an issue as Not A Defect Closing this issue. If there are further queries, please raise a new JIRA request Jenkins / JENKINS-41314 Selections of trunk and branches of projects from PTC integrity for build Change By: PTC ALM Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-32826) Polling failure on jobs with same name in different folders
Title: Message Title PTC ALM closed an issue as Won't Fix Closing this issue due to non-support for older release. If there are further queries, please raise a new JIRA request Jenkins / JENKINS-32826 Polling failure on jobs with same name in different folders Change By: PTC ALM Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33079) Handling prebuild checkpoint results in Pipeline
Title: Message Title PTC ALM closed an issue as Not A Defect Closing this issue. If there are further queries, please raise a new JIRA request Jenkins / JENKINS-33079 Handling prebuild checkpoint results in Pipeline Change By: PTC ALM Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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,
[JIRA] (JENKINS-41054) PTC plugin failed to timeout
Title: Message Title PTC ALM commented on JENKINS-41054 Re: PTC plugin failed to timeout Based on the first exception(original job), can you try increasing the Checkout thread timeout parameter in the old job configuration to something greater than the default 5 mins? Say 10 mins or 15 mins and recheck. I am not entirely sure why a new job would throw a Derby SQL exception. Just a couple of things for my understanding: did you 'copy' the existing job or created a brand new one from scratch? Also can you send across the IntegritySCM log for this scenario, if you can. The IntegritySCM logger setup can be found here: https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin#PTCIntegrityPlugin-Troubleshooting Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41314) Selections of trunk and branches of projects from PTC integrity for build
Title: Message Title PTC ALM commented on JENKINS-41314 Re: Selections of trunk and branches of projects from PTC integrity for build Hi Sudarshan, Regarding your first question, yes if you don't specify a development path (#d=) or any other config path parameters(e.g. #b), this would result in the current mainline/trunk getting referenced. For the second question, Jenkins will reference Integrity Projects from an Integrity Server (and not from a sandbox). Jenkins will check out (si projectco command) the mainline (or development path) for that project, depending on the configuration path specified in Jenkins and build the same. Irrespective of how your local sandbox is set up, configuration wise, it has no linkage with how Jenkins interacts with the Integrity Server. Whatever configuration path you specify in Jenkins (mainline/devpath/build), it checks out that project structure with the specified configuration directly from the Integrity Server. Hope that helps! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41019) Check in into subfolder of current project
Title: Message Title PTC ALM commented on JENKINS-41019 Re: Check in into subfolder of current project Trying to reproduce the problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41054) PTC plugin failed to timeout
Title: Message Title PTC ALM commented on JENKINS-41054 Re: PTC plugin failed to timeout Its recommended to recreate the jobs, since we changed some of the code that relate to how the jobs are referred to in the Derby database. Not doing so may result in the "Table/View 'SCM_C380AD5E_FCBF_4350_8B88_0FE304E3C602' does not exist." sort of errors, that was there in the log you posted. We did put some precaution in for this error not to happen, if we did just a re-save, but not completely guaranteed. The checkpoint error looks to be because because si checkpoint is happening at the time of some other operation that might be affecting the repository at the same time. The stacktrace on the Integrity Server would be more helpful in this case to diagnose (if this happening frequently). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41054) PTC pplugin failed to timeout
Title: Message Title PTC ALM commented on JENKINS-41054 Re: PTC pplugin failed to timeout Hi Grigoriy, Have you re-created the build jobs post the upgrade to 2.0.2? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31836) Restarting PTC server during Polling does not time out
Title: Message Title PTC ALM resolved as Fixed Fixed in release 2.0.2 Jenkins / JENKINS-31836 Restarting PTC server during Polling does not time out Change By: PTC ALM Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33077) checkPointBeforeBuild fails for projects on development path
Title: Message Title PTC ALM stopped work on JENKINS-33077 Change By: PTC ALM Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33475) Authentification based on project specific username and password fails if system account is not set
Title: Message Title PTC ALM resolved as Fixed Fixed in release 2.0.2 Jenkins / JENKINS-33475 Authentification based on project specific username and password fails if system account is not set Change By: PTC ALM Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-33077) checkPointBeforeBuild fails for projects on development path
Title: Message Title PTC ALM resolved as Fixed Fixed in release 2.0.2 Jenkins / JENKINS-33077 checkPointBeforeBuild fails for projects on development path Change By: PTC ALM Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus, I tried figuring out the problem from the server logs that you sent. However, I am unable to diagnose the problem that the Integrity Server is throwing up in your case. Since this is not a problem with the plugin as such and the Integrity Server is throwing up an exception, we recommend contacting the PTC ILM Tech support team so they can look into your environment and see why the Integrity Server is throwing up an exception in your case, Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus, Please uncomment the below loggers in logger.properties file to enable them. 1. #mksis.logger.message.includeCategory.API=10 2. #mksis.logger.exception.includeCategory.API=10 3. #mksis.logger.message.includeCategory.DEBUG=10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus, Will you able to get the server logs soon? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title PTC ALM commented on JENKINS-31739 Re: NPE from IntegritySCM.checkout from Workflow Matthias Rump, can you confirm if we are still seeing this issue with 2.0/2.0.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34158) No information about changes displayed
Title: Message Title PTC ALM commented on JENKINS-34158 Re: No information about changes displayed This is related to JENKINS-33420 Multiple-scm plugin forces clean workpace for every build for Integrity Plugin. Since multiple SCM plugin forces a clean workspace for every build, no changes are recorded, as changelog functionality comes into picture only during incremental builds. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33522) Server session not closed
Title: Message Title PTC ALM resolved as Duplicate Jenkins / JENKINS-33522 Server session not closed Change By: PTC ALM Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33522) Server session not closed
Title: Message Title PTC ALM closed an issue as Fixed Jenkins / JENKINS-33522 Server session not closed Change By: PTC ALM Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33522) Server session not closed
Title: Message Title PTC ALM reopened an issue Jenkins / JENKINS-33522 Server session not closed Change By: PTC ALM Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title PTC ALM edited a comment on JENKINS-31739 Re: NPE from IntegritySCM.checkout from Workflow Are we able to reproduce this with plugin version 2.0 .1 /2.0. 2 1 ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus, The config xml shows a few plugins installed, but we don't think those are connected with this issue. After a bit of digging in, we believe what is happening is that Integrity Server is not returning back the checkpoint revision (after successfully checkpointing in Integrity), so when the plugin tries to read the Integrity-returned checkpoint, it is not able to do so and throws up this error. Could you check/attach the Integrity server log for this specific case and see if it shows up any error while returning back a response for the checkpoint operation? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM edited a comment on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus,Thanks for the log. It is surprising that the IntegritySCM log shows post build si checkpoint successful:si checkpoint --user=build_User --port=7002 --hostname=company-ptc13 --project=#p=p:/Projects/User/User.pj#s=Software/Software.pj#s=Service/Service.pj#s=src.main/src.main.pj --label=PUser_ServiceSw_x86_0.1.1610.06002_Test --description=PUser_ServiceSw_x86_0.1.1610.06002_Test -- returned exit code 0 but the console log throws up an error. Are you using any other SCM plugins in conjunction with the Integrity plugin? Also is it possible for you to share your job configuration so that we can see any anomaly? You can get the job configuration xml file using http://:8080/jenkins/job//config.xml .Also please let us know the Integrity Server version you are using. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus, Thanks for the log. It is surprising that the IntegritySCM log shows post build si checkpoint successful: si checkpoint --user=build_User --port=7002 --hostname=company-ptc13 --project=#p=p:/Projects/User/User.pj#s=Software/Software.pj#s=Service/Service.pj#s=src.main/src.main.pj --label=PUser_ServiceSw_x86_0.1.1610.06002_Test --description=PUser_ServiceSw_x86_0.1.1610.06002_Test – returned exit code 0 but the console log throws up an error. Are you using any other SCM plugins in conjunction with the Integrity plugin? Also is it possible for you to share your job configuration so that we can see any anomaly? You can get the job configuration xml file using http://:8080/jenkins/job//config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33079) Handling prebuild checkpoint results in Pipeline
Title: Message Title
PTC ALM commented on JENKINS-33079
Re: Handling prebuild checkpoint results in Pipeline
Hi Matthias, Whenever the MKSSI_BUILD environment variable is updated, the MKSSI_PROJECT (the si project configuration path) environment variable is updated just before it as below from the plugin codebase:
env.put("MKSSI_PROJECT", siProject.getConfigurationPath());
env.put("MKSSI_BUILD", siProject.getProjectRevision());
MKSSI_BUILD & MKSSI_PROJECT variables are coupled with each other even for parallel pipeline builds and can be used to identify each other in context.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus, we tried reproducing this issue with a #s project configuration, but unable to reproduce this. Could you attach the IntegritySCM log (Log Level : All ) for the entire build (Refer Troubleshooting section in https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin%20#Troubleshooting) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33077) checkPointBeforeBuild fails for projects on development path
Title: Message Title PTC ALM started work on JENKINS-33077 Change By: PTC ALM Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title PTC ALM commented on JENKINS-31739 Re: NPE from IntegritySCM.checkout from Workflow Are we able to reproduce this with plugin version 2.0.1/2.0.2? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38333) Jenkins can't visit update-center
Title: Message Title PTC ALM closed an issue as Duplicate Jenkins / JENKINS-38333 Jenkins can't visit update-center Change By: PTC ALM Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38333) Jenkins can't visit update-center
Title: Message Title PTC ALM commented on JENKINS-38333 Re: Jenkins can't visit update-center Closing as duplicate of JENKINS-38262 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [integrity-plugin] (JENKINS-33077) checkPointBeforeBuild fails for projects on development path
Title: Message Title PTC ALM commented on JENKINS-33077 Re: checkPointBeforeBuild fails for projects on development path This will be resolved in the next plugin iteration viz. 2.0.2 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] [integrity-plugin] (JENKINS-33420) Multiple-scm plugin forces clean workpace for every build for Integrity Plugin
Title: Message Title PTC ALM updated an issue Jenkins / JENKINS-33420 Multiple-scm plugin forces clean workpace for every build for Integrity Plugin Change By: PTC ALM Labels: 2.0.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] [integrity-plugin] (JENKINS-33420) Multiple-scm plugin forces clean workpace for every build for Integrity Plugin
Title: Message Title PTC ALM created an issue Jenkins / JENKINS-33420 Multiple-scm plugin forces clean workpace for every build for Integrity Plugin Issue Type: Improvement Assignee: PTC ALM Components: integrity-plugin Created: 09/Mar/16 9:26 AM Priority: Major Reporter: PTC ALM multiple-scm plugin forces Integrity plugin to do a clean workspace every time a build is triggered, even though Clean Workspace option is disabled. The multiple-scm plugin bypasses the calcRevisionsFromBuild() method in IntegritySCM class which forces every IntegritySCM.checkout to trigger with a null baseline SCMRevisionState parameter and leads to a clean copy everytime. Add Comment
[JIRA] [integrity-plugin] (JENKINS-32665) Test bug
Title: Message Title PTC ALM created an issue Jenkins / JENKINS-32665 Test bug Issue Type: Bug Assignee: PTC ALM Components: integrity-plugin Created: 28/Jan/16 7:53 AM Priority: Minor Reporter: PTC ALM Test Bug Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [integrity-plugin] (JENKINS-32665) Test bug
Title: Message Title PTC ALM closed an issue as Not A Defect Jenkins / JENKINS-32665 Test bug Change By: PTC ALM Status: Open Closed Resolution: Not A Defect 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.
