[ https://issues.jenkins-ci.org/browse/JENKINS-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161044#comment-161044 ]
Cletus D'Souza commented on JENKINS-13220: ------------------------------------------ If the new files are showing up in the 'si viewproject' output, then this would be a bug with the core Source product/api. Can you please check the 'si viewproject' output to see if this is the case? > The integration inconsistently handles change packages that are submitted but > not yet accepted. > ----------------------------------------------------------------------------------------------- > > Key: JENKINS-13220 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13220 > Project: Jenkins > Issue Type: Bug > Components: integrity-plugin > Affects Versions: current > Environment: Linux/x64. > Reporter: Eric Youngdale > Assignee: Cletus D'Souza > Labels: plugins > > We had an issue whereby there were a set of changes which were submitted but > not yet accepted into MKS Source. Some of the changes involved new source > files (JUnit tests in this case), and others involved changes to existing > files. > What I am seeing is that regarding changes to existing files, the plugin > correctly does not download them until the change package is eventually > accepted. However for any new files, this isn't the case - it downloads the > immediately no matter what the status of the change package. > In our case the new JUnit tests were being automatically run even though the > corresponding changes had not yet been applied and it caused the build to > fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira