We should be creating the release branches for all those repositories at the
same time.
> On Apr 22, 2019, at 1:56 PM, Dan Smith wrote:
>
> Hi devs,
>
> I'm looking at trying to automate some of the geode release steps, but one
> thing I noticed is that we are inconsistent about when or if we
Hi devs,
I'm looking at trying to automate some of the geode release steps, but one
thing I noticed is that we are inconsistent about when or if we create a
release branch in our different repos that we release (geode,
geode-examples, geode-native). For geode, we create a branch when we start
the
These test require you to have the Chrome Driver from Selenium. You can
find it here
https://github.com/SeleniumHQ/selenium/wiki/ChromeDriver
If you are on a Mac, you can probably (haven't tested this in awhile) use
brew with this command
brew cask install chromedriver
-michael
On Mon, Apr
Is there a way to run a geode-pulse uiTest on the command-line without it
failing due to "webdriver.chrome.driver system property"? I would expect
the gradle build to be setting this property.
$ ./gradlew geode-pulse:uiTest --tests PulseAuthorizationTest
...
> Task :geode-pulse:uiTest
Owen and I talked to Kirk and Aaron. It sounds like this issue does not
need to hold up release 1.9.0 because it's been in all previous versions.
If we need to create another RC we will get this fix in there.
-Dan
On Fri, Apr 19, 2019 at 1:50 PM Owen Nichols wrote:
> Hi Aaron, Kirk and Geode
I think I gave you permissions for this. Let me know if it doesn't work for
you. Thanks!
On Mon, Apr 22, 2019 at 7:16 AM Owen Nichols wrote:
> As per Geode release manager instructions, I will need to bulk-transition
> resolved issues to completed (once we have voted to release a 1.9.0 RC).
>
As per Geode release manager instructions, I will need to bulk-transition
resolved issues to completed (once we have voted to release a 1.9.0 RC).
Please grant me Jira 'bulk-transition’ permissions.
Thanks,
-Owen
