[JIRA] (JENKINS-57922) Ability to specify output directory for translation-tool.pl
Title: Message Title Mustafa Ulu resolved as Fixed Jenkins / JENKINS-57922 Ability to specify output directory for translation-tool.pl Change By: Mustafa Ulu Status: Open Resolved Resolution: Fixed 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.199895.156010731.10956.1571515560332%40Atlassian.JIRA.
[JIRA] (JENKINS-57922) Ability to specify output directory for translation-tool.pl
Title: Message Title Mustafa Ulu assigned an issue to Mustafa Ulu Jenkins / JENKINS-57922 Ability to specify output directory for translation-tool.pl Change By: Mustafa Ulu Assignee: Mustafa Ulu 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199895.156010731.25232.1560266520106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57922) Ability to specify output directory for translation-tool.pl
Title: Message Title Mustafa Ulu created an issue Jenkins / JENKINS-57922 Ability to specify output directory for translation-tool.pl Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-06-09 19:08 Labels: localization translation Priority: Minor Reporter: Mustafa Ulu Adding ability to specify output directory to translation-tool.pl will make the life of localization plugin (see JEP-216) developers quite easy. Localization plugins will put localization files inside language plugins. Those plugins will have the same directory layout as core. Currently plugin developers can only manually synchronize their translation. Add Comment
[JIRA] (JENKINS-57919) Naming Turkish localization plugin
Title: Message Title Mustafa Ulu commented on JENKINS-57919 Re: Naming Turkish localization plugin I have created a hosting request: https://issues.jenkins-ci.org/browse/HOSTING-783 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199891.1560016046000.24073.1560091800093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57919) Naming Turkish localization plugin
Title: Message Title Mustafa Ulu updated an issue Jenkins / JENKINS-57919 Naming Turkish localization plugin Change By: Mustafa Ulu URL: https://github.com/mustafau/localization-tr- tr- plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199891.1560016046000.24039.1560076380135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57919) Naming Turkish localization plugin
Title: Message Title Mustafa Ulu commented on JENKINS-57919 Re: Naming Turkish localization plugin Thanks for your time. I will use following names: Repository: localization-tr-plugin.git Artifact: localization-tr.hpi 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199891.1560016046000.24037.1560075780271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57919) Naming Turkish localization plugin
Title: Message Title Mustafa Ulu created an issue Jenkins / JENKINS-57919 Naming Turkish localization plugin Issue Type: Improvement Assignee: Daniel Beck Components: localization-support-plugin Created: 2019-06-08 17:47 Labels: localization Priority: Minor Reporter: Mustafa Ulu What should be the artifact id of a Turkish localization plugin? According to JEP-216, the artifact id must include the country code (localization-[language code]-[country code]-plugin), but Turkish localization files inside Jenkins do not contain country code (Messages_tr.properties). Should I name the artifact as "localization-tr-tr-plugin" and rename all files to "Messages_tr_TR.properties" or is the name "localization-tr-plugin" enough? Add Comment
[JIRA] (JENKINS-38476) Always use "-usenonexclusivelock" option
Title: Message Title Mustafa Ulu closed an issue as Won't Fix Not that useful. Jenkins / JENKINS-38476 Always use "-usenonexclusivelock" option Change By: Mustafa Ulu 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20797) UserIdCause should be used, not UserCause
Title: Message Title Mustafa Ulu commented on JENKINS-20797 Re: UserIdCause should be used, not UserCause I have submitted a PR to fix this. https://github.com/jenkinsci/release-plugin/pull/20 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-20797) UserIdCause should be used, not UserCause
Title: Message Title Mustafa Ulu reopened an issue Release button still triggers UserCause not UserIdCause. See https://github.com/jenkinsci/release-plugin/blob/master/src/main/java/hudson/plugins/release/ReleaseWrapper.java#L695 Jenkins / JENKINS-20797 UserIdCause should be used, not UserCause Change By: Mustafa Ulu Resolution: Fixed Status: Resolved 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,
[JIRA] (JENKINS-38476) Always use "-usenonexclusivelock" option
Title: Message Title Mustafa Ulu created an issue Jenkins / JENKINS-38476 Always use "-usenonexclusivelock" option Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2016/Sep/23 8:50 PM Priority: Minor Reporter: Mustafa Ulu I believe WebLogic Deployer Plugin fits the definition of "-usenonexclusivelock" option perfectly: Deployment operation uses an existing lock, already acquired by the same user, on the domain. This option is helpful in environments where multiple deployment tools are used simultaneously and one of the tools has already acquired a lock on the domain configuration. https://docs.oracle.com/cd/E13222_01/wls/docs103/deployment/wldeployer.html Add Comment
[JIRA] (JENKINS-37464) Add ability to specify multiple deployment policy groups
Title: Message Title Mustafa Ulu commented on JENKINS-37464 Re: Add ability to specify multiple deployment policy groups I have submitted the PR. Tested with a job which is configured with all 8 causes. After the update, job is loaded successfully with 6 causes. 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-37464) Add ability to specify multiple deployment policy groups
Title: Message Title Mustafa Ulu commented on JENKINS-37464 Re: Add ability to specify multiple deployment policy groups Hi, Thanks for the comment. I didn't bother to support deprecated Causes in this implementation. Do people still use LegacyCodeCause and UserCause? If so I will add them. Regards. 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-37464) Add ability to specify multiple deployment policy groups
Title: Message Title Mustafa Ulu commented on JENKINS-37464 Re: Add ability to specify multiple deployment policy groups Attaching my progress so far. I implemented an improved version of the second approach (similar to GitSCM plugin's extension approach) This will be backwards compatible and easily extendable. 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-37464) Add ability to specify multiple deployment policy groups
Title: Message Title Mustafa Ulu updated an issue Jenkins / JENKINS-37464 Add ability to specify multiple deployment policy groups Change By: Mustafa Ulu Attachment: Screen Shot 2016-08-21 at 11.10.40.png 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-37464) Add ability to specify multiple deployment policy groups
Title: Message Title Mustafa Ulu created an issue Jenkins / JENKINS-37464 Add ability to specify multiple deployment policy groups Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2016/Aug/17 10:55 AM Labels: weblogic Priority: Minor Reporter: Mustafa Ulu Current configuration options does not cover every possible deployment policy scenarios. For example: Deploy when there is "SCM change" if build is started by build timer Deploy regardless of "SCM change" if build is started by user In order to achive this, plugin should group "Deployment policy" and "SCM change" options together and allow user to specify as much group as possible. Another option is to extend deployment policy list for all possible scenarios. This should be easier to implement and understand. For example: Started by user Started by user (There is SCM change) Started by build timer Started by build timer (There is SCM change) ... I will submit a PR with second approach soon. Which approach has better chance of acceptance?
[JIRA] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there are no changes
Title: Message Title Mustafa Ulu commented on JENKINS-19962 Re: Add the ability to declare a job successful even if there are no changes This works when mustExitOnFailure is set to false. If mustExitOnFailure is true build still fails if there are no changes. I will send another PR. 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there are no changes
Title: Message Title Mustafa Ulu commented on JENKINS-19962 Re: Add the ability to declare a job successful even if there are no changes Hi, I am already working on a pr. To me this should be the default behaviour and there should be no configuration option for it. Out of six WebLogicPreRequisteStatusS only UNSATISFIED_DEPENDENCIES should modify build result. Others should just return. If this is acceptable I can submit a pr soon. If not I will start working on a configuration option. 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there are no changes
Title: Message Title Mustafa Ulu updated an issue Jenkins / JENKINS-19962 Add the ability to declare a job successful even if there are no changes Change By: Mustafa Ulu Summary: Add the ability to declare a job successful even if there 's are no changes 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there's no changes
Title: Message Title Mustafa Ulu commented on JENKINS-19962 Re: Add the ability to declare a job successful even if there's no changes Any progress on this issue? I would like to help implement it. 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there's no changes
Title: Message Title Mustafa Ulu updated an issue Jenkins / JENKINS-19962 Add the ability to declare a job successful even if there's no changes Change By: Mustafa Ulu Hello, I run some builds every night. I force the execution of those builds because of some quality analysis of projectsEach one has a "post-build action" which deploys on weblogic server. In order to reduce the server load and to only deploy the updated projects I mark the option "Deploying only when sources changes".In some projects, the status is unstable even the unit tests are good.I saw on a previous issue (JENKINS-19016) that you changed the job's status from "FAILED" to "UNSTABLE". However,it would be nice if this behaviour could be customizable ( eg . add some radio button to choose the expected behaviour.Thanks.Regards 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.
