Skip to content

Jenkins integration - #1

Open
Brian Hyams (brianhy) wants to merge 12 commits into
masterfrom
jenkins-integration
Open

Jenkins integration#1
Brian Hyams (brianhy) wants to merge 12 commits into
masterfrom
jenkins-integration

Conversation

@brianhy

Copy link
Copy Markdown

Preliminary Jenkins integration

Jenkins will need this checked in before it'll actually run, so we need to check-in, then run, then debug any issues.

No changes to the project itself yet.
When this is present the build will break on the mac b/c it doesn't have .net 4.6 installed.  Instead of trying to work around that (which isn't needed since we want netstandard for .net core support), we instead deprecate it.

We didn't go so far as to remove the .Net framework dirs as that would result in lots of git merge issues if we take new drops from master.
@discoci2

Copy link
Copy Markdown

🚀 This PR has been checked for open source licensing and security compliance.

Analysis Results:

 Test Passed! 0 issues found
 

For more information, see:

In Jenkins, a PR isn't run from the branch, so the releaseBranch check wasn't doing anything.  Instead, we'll just always run the publish to test publish to artifactory.
Nuget publish succeeded, but I don't see it in nuget.  The log output makes me wonder if the build # is problematic:
> 12:01:45 Build successfully deployed. Browse it in Artifactory under https://csdisco.jfrog.io/csdisco/webapp/builds/csdisco-ical-net%20::%20PR-1/3
Now that build description will include build version, we need to feed that to the build.ps1 to keep those in sync.
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.

2 participants