[JIRA] (JENKINS-51980) Missing Build Trigger Section after Upgrade of Jenkins
Title: Message Title Christian Schmitt commented on JENKINS-51980 Re: Missing Build Trigger Section after Upgrade of Jenkins Facing the same issue. And unfortunately moving to the multibranch pipeline plugin is not an option for us since the lack of some features (e.g. incremental maven module builds)... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191476.1529169756000.4723.1578486481090%40Atlassian.JIRA.
[JIRA] (JENKINS-60496) Support for incremental maven module build
Title: Message Title Christian Schmitt created an issue Jenkins / JENKINS-60496 Support for incremental maven module build Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-12-16 09:28 Labels: maven incrementals feature-request pipeline-maven Priority: Minor Reporter: Christian Schmitt Until now we used to process multibranch maven projects with the Multi-Branch Project Plugin which under the hood uses the maven-project-plugin for maven builds. This maven-project-plugin has this great feature for doing incremental builds - meaning just rebuild the maven modules which have changed in the SCM since the last build. We used this feature heavily beacause we have many multimodule maven projects (also multi levels) and this feature could decrease build times fundamentally. Now the Multi-Branch Project Plugin is deprecated and we are advised to move to the Pipeline-Multibranch Plugin. This plugin uses the pipeline-maven-plugin under the hood for maven builds. In this plugin we are missing an incremental build mechanism. Build times would increase dramatically. Is there any hope to get this feaure also into the pipeline-maven-plugin? Thanks and best Regards Christian
[JIRA] (JENKINS-60331) Checkout over SSH not working anymore after restarting jenkins
Title: Message Title Christian Schmitt created an issue Jenkins / JENKINS-60331 Checkout over SSH not working anymore after restarting jenkins Issue Type: Bug Assignee: Unassigned Components: gitea-plugin Created: 2019-11-29 13:38 Environment: Jenkins 2.190.3 gitea-plugin 1.1.2 Priority: Major Reporter: Christian Schmitt Gitea organization configured with "Checkout over SSH" Using a private key from the jenkins credential store or adding one (since "use build agents key" also not working :-/ ) Then it's Initially working After a Jenkins restart git commands are falling back to https When triggering "Scan Gitea Organization Now" it's working again till next restart Similar to JENKINS-46094
[JIRA] (JENKINS-58230) how to disable automatic build by default?
Title: Message Title Christian Schmitt commented on JENKINS-58230 Re: how to disable automatic build by default? I have a slightly different use case. Problem is that filtering "Branch names to build automatically" would also disable the trigger at SCM changes (e.g. pushes) which we like to keep. I'm just trying to supress the initial build right after the branch discovery. Is there a way to achive this? tl;dr=: We are using a multi repo setup for a single product with many related maven builds (which have dependencies from each other). For creating feature/release/hotfix branches we like to use a seed job in jenkins (using jgitflow). In our tests this job created the branch in every related repo but then unfortunately executed the build for the new branch automatically. Problem is that at this point the depended artifacts are not yet available on our central maven repository because depended builds have not finished yet. We need to find a way to execute the branch creation + initial build sequencially for each repo. Supressing the initial build after branch discovery would be the easiest way. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200291.156160679.4035.1572341160149%40Atlassian.JIRA.
