[
https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-15059:
------------------------------------------
* PR for MASTER:
https://github.com/jbosstools/jbosstools-openshift/pull/183
* PR for CR1:
https://github.com/jbosstools/jbosstools-openshift/pull/184
pushed to upstream master. Waiting for review for CR1.
Server adapter: tells me that there are local commit that I can
publish even though there are none
--------------------------------------------------------------------------------------------------
Key: JBIDE-15059
URL:
https://issues.jboss.org/browse/JBIDE-15059
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.2.0.Alpha1
Attachments: already-up-to-date.png, committed-changes-to-publish.png
1. EXEC: launch OpenShift Application wizard
2. EXEC: create a new application and have it imported to your workspace
3. EXEC: After the import the adapter will tell you that there are local commits that you
may want to publish to OpenShift. Tell it to do so
!committed-changes-to-publish.png!
4. EXEC: Pick your server adapter and tell it to publish to OpenShift
Result:
The adapter tells you that you that there are local commits that you may push.
!committed-changes-to-publish.png!
Expected:
We just pushed there cannot be local commits that were not pushed yet
5. EXEC: Confirm the dialog and tell it to publish
Result:
It tells you that OpenShift is already up-to-date (which is true!)
!already-up-to-date.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira