search

jenkinsci / salesforce-migration-assistant-plugin

Salesforce Migration Assistant plugin for Jenkins CI
https://plugins.jenkins.io/salesforce-migration-assistant-plugin/
MIT License
29 stars 15 forks source link

Add support for other git hosting providers #8

Open aesanch2 opened 8 years ago

aesanch2 commented 8 years ago

Investigate possible issues with:

Add any other potential hosts as needed.

TheWallOfDucks commented 8 years ago

Is the issue being experienced with BitBucket just not being able to diff two commits? We have just recently started trying to use your plugin to pull from BitBucket and then deploy to SF orgs but it just seems to deploy blank change sets with no meta data. Are these the symptoms of the issue you are looking to address?

Thanks for your work on the plugin, would be a huge benefit to our company if we can get it to work.

Caleb

aesanch2 commented 8 years ago

@TheWallOfDucks it probably is something along those lines. There might be some differences between how Jenkins stores commit information depending on who the remote service is.

I'll do my best to try and dig into this, but feel free to fork the project and experiment as well!

gcoogle commented 7 years ago

If we use BitBucket, how could that affect the plugin? When I run a build, the job does show that I've committed changes since the run of the job. This is when it checks the SCM, before it does the build step for the plugin.

@TheWallOfDucks - if this uses the Metadata API, it would deploy using Packages if I'm not mistaken. I haven't used it before, but I wouldn't think it would display as a Change Set in the SF org you are deploying to. Would it really display under Inbound Change Sets? If so, then that step hasn't occured on my runs. They mostly error out, but I did get the job to run successful a few times with the plugin. No update was reflected in the sandbox on the Apex Class I added a comment to.