-
Notifications
You must be signed in to change notification settings - Fork 54
Add support for uploading multiple builds to the same version #52
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
Conversation
|
Hi @Azhrei251 thanks for this pull request. Can you do a few things for me please. Could you add in a little description of the problem this solves? I can have a guess by looking at the code but I don't want to make assumptions about it. You should be able to edit the description in PR. Secondly the PR has merge conflicts that will need to be resolved you can do this by updating your feature branch with the latest from the master branch in the upstream repository. Thirdly are there any tests that you could add for this? I don't really use HokeyApp like this but instead upload a single build to a pre-existing project so I want to have some more confidence in the form of a unit test. And finally, I'm sure you've noticed but, the class I do appreciate that the rest of the plugin code base isn't like this but I'd like to refactor it in the future so that it is easier to work with so need to start laying down some standards in the interim. Anyways, thanks for the help! |
|
Hey @mezpahlan, thanks for the response. For your comments:
Let me know if there's anything else. Thanks! |
mezpahlan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @jenkinsci/code-reviewers would one of you mind taking a look at the comment I left in VersionCreation.java in this PR. The PR looks promising but I was wondering about what to do regarding maintaining backward compatibility and the strategies to deal with that. Thanks.
|
|
||
| @DataBoundConstructor | ||
| public VersionCreation(String appId) { | ||
| public VersionCreation(String appId, String versionCode) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @jenkinsci/code-reviewers we've received this PR that looks promising, however I want to check what the right thing to do is with this public method now that it is changing. I gather we don't want to break things for anyone that relies on the API exposed publicly by this plugin. Would it be better to add an overload in this case and default the second parameter? Many thanks.
oleg-nenashev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Formally it breaks binary compatibility. I woul recommend having a compat constructor which may be marked as depeecated
|
I've added an overload constructor as recommended |
|
Hi, unfortunately this PR is not backward compatible. Now I'm getting: My current configuration was: |
|
I have no idea how jenkins plugins works but I think that old constructor shouldn't be deprecated and it still should have this |
|
Hi @MikolajKakol I've created a bug in the issue tracker. Let's continue the discussion over there for now until we can create another PR. Thanks. |
This PR allows users to specify a version number to upload their builds to. This allows for more than one build to be referenced to the same version.
The issue initially faced was uploading a new version every build was quickly getting out of hand, and finding specific historic builds (those released to the public) in the app was becoming difficult. Uploading several builds to the same version cuts down on the number of internal versions being shown in-app.