Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added generic DSL support using metadata from Descriptors #816

Merged
merged 1 commit into from
Apr 18, 2016
Merged

added generic DSL support using metadata from Descriptors #816

merged 1 commit into from
Apr 18, 2016

Conversation

daspilker
Copy link
Member

No description provided.

@jenkinsadmin
Copy link
Member

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.

@daspilker
Copy link
Member Author

@v1v
Copy link
Member

v1v commented Apr 9, 2016

👍

@@ -1,3 +1,3 @@
version=1.46-SNAPSHOT
groovyVersion=1.8.9
githubUser=jenkinsci
githubUser=daspilker
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change should probably be reverted, or?

@daspilker
Copy link
Member Author

@sschuberth thanks for the review, I removed those files from the commit

@daspilker daspilker merged commit 843ac64 into jenkinsci:master Apr 18, 2016
@chbloemer
Copy link

@daspilker is it possible to use the performance plugin with generic dsl? See: https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin

@daspilker
Copy link
Member Author

@chbloemer yes, it's possible

@daspilker daspilker deleted the symbols branch May 10, 2016 20:17
@itavero
Copy link
Member

itavero commented May 11, 2016

Is this included in release 1.46?

Update
I'm asking this because it does not work for me when I'm applying the "DSL Factory" pattern from the wiki.
I've added some additional information to the JIRA issue that should be "fixed" with this new feature:
https://issues.jenkins-ci.org/browse/JENKINS-22138

@sschuberth
Copy link
Member

@itavero According to the release notes, yes.

@itavero
Copy link
Member

itavero commented May 11, 2016

So, I got a hunch why this does not work. As mentioned in the comment I added to JENKINS-22138, I'm running the script locally.
I reckon I need to add the plug-in to my classpath or something, right?

@itavero
Copy link
Member

itavero commented May 11, 2016

Totally missed this page, Automatically Generated DSL, which mentions some limitations in the last few paragraphs.
What I'm trying to achieve is not yet possible. 😉

@ghost
Copy link

ghost commented Oct 9, 2017

I am encountering problem while trying to automate the job creation process.
Target repository field is empty after trying multiple times.
below is the code I am using.

Any solutions how that value can be populated, or any other way to integrate DSL with artifactory that solves the problem.
I could not find any help on google and ended up with this same issue discussed here.
I am using the latest version of DSL plugin .

configure { project ->
project / buildWrappers << 'org.jfrog.hudson.generic.ArtifactoryGenericConfigurator' {
details {
artifactoryUrl('abc')
artifactoryName('abc')
deployReleaseRepository
{
keyFromText('node-plugin-release-local') keyFromSelect('') dynamicMode(true)

{color:#ff0000}}
}
deployPattern('.zip ')
matrixParams('')
deployBuildInfo(true)
includeEnvVars(true)
envVarsPatterns {
includePatterns('')
excludePatterns('password,secret,key')
}
discardOldBuilds(true)
discardBuildArtifacts(true)
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants