-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add octopus.push.package step support #53
Add octopus.push.package step support #53
Conversation
b4213a0
to
ead09ff
Compare
Hello @ss-remygreinhofer , sorry for not getting to this sooner! Thanks a lot for your contribution - however, would it be possible to add some tests that cover the usage for the new step type? Recently, I'm trying to refactor tests to testify suites in order to deal with some isolation and cleanup issues I've had in the past. Take a look at 7ef46f9 and if you need any help adding test scenarios, let me know! |
No problem, I'll work on some testify tests. |
ead09ff
to
aceb9ed
Compare
I just rebased my branch and although Travis gives me the green mark, the tests fail on my machine:
I'm not sure wether it is a platform difference, or a go version problem.
EDIT |
You can scratch the previous comment, I forgot to set the This led me to write a |
@cvbarros I added some tests to ensure the new step can be created and added (I did the same thing you did for the PowerShell step) and I updated the setup to install the Octopus plugin automatically. I did include PR #57 into this one as it seems clearer to me that way, but in case you reject it for some reason, I could figure out a way around it. |
I've merged #57 first, sorry missed the comment. I think after a rebase this will be good to be merged! |
This patch implements the support for Octopus (https://octopus.com/docs/api-and-integration/teamcity). It allows to define a new type of build step: "octopus.push.package".
Upstream updated the Step interface. This patch makes sure that the Octopus steps implement it correctly.
2f7c40d
to
6a85f20
Compare
The branch is rebased. Testify looks like a great framework, and the reference in the Go world for asserting and mocking, but my experience is too limited to provide you with valuable feedback. Besides I just mirrored what you did for the PowerShell step, so it was very straightforward. Let me send you a few more PRs and I'll have an opinion 😉 |
Nice! Thanks a lot for the contribution, going to merge this. |
This patch implements the support for Octopus
(https://octopus.com/docs/api-and-integration/teamcity). It allows to
define a new type of build step: "octopus.push.package".