profile
viewpoint
Danny Thomas DanielThomas @Netflix Los Gatos, California Developer Productivity @ Netflix

DanielThomas/ec2gaming 100

EC2 Gaming on macOS with Steam In-Home Streaming

DanielThomas/dotfiles 13

Opinionated dotfiles for Mac OS with zsh

DanielThomas/groundhog 8

Simple, high performance HTTP capture and replay

DanielThomas/advent 0

Advent of Code

DanielThomas/artifactory-user-plugins 0

Sample Artifactory User Plugins

DanielThomas/clouddriver 0

read and write operations across cloud providers

DanielThomas/deck 0

Management UI for Spinnaker

DanielThomas/frigga 0

Utilities for working with Asgard named objects

DanielThomas/genie 0

Federated Job Execution Engine

DanielThomas/go-left-pad 0

String left pad

issue commentnebula-plugins/nebula-project-plugin

Update ElasticSearch dependency to a more recent version

@rpalcolea Any news on this? Seems like you are updating gradle versions on regular bases. Can you please answer my question?

danielbraeutigam

comment created time in 2 hours

pull request commentnebula-plugins/gradle-dependency-lock-plugin

Use `size` accessor

Coverage Status

Coverage remained the same at 74.93% when pulling 3fd29219248e1163b888861d3579c16fa1f5d24f on bmuskalla:patch-1 into 0d34458e41982c74b5359c04e1890a05e5300c91 on nebula-plugins:master.

bmuskalla

comment created time in 3 hours

PR opened nebula-plugins/gradle-dependency-lock-plugin

Use `size` accessor

The resolution alternatives are checked using the private size field which may not exist for all potential List implementations.

+1 -1

0 comment

1 changed file

pr created time in 3 hours

created tagnebula-plugins/gradle-dependency-lock-plugin

tagv11.1.0

A plugin to allow people using dynamic dependency versions to lock them to specific versions.

created time in 18 hours

IssuesEvent

push eventnebula-plugins/gradle-resolution-rules-plugin

Aubrey Chipman

commit sha 9e6f898dc125c6f9c5746e3aebcef85eb6cc3cbe

Use Kotlin 1.4.10

view details

push time in 6 days

delete branch nebula-plugins/gradle-dependency-lock-plugin

delete branch : kotlin-1.4.10

delete time in 6 days

push eventnebula-plugins/gradle-dependency-lock-plugin

Aubrey Chipman

commit sha 6712ac9688f8847799b46a57755fe861e5c88072

Use Kotlin 1.4.10 and add explicit Java 1.8 configuration Gradle 6.7.1 is tested through Kotlin 1.4.0 (https://docs.gradle.org/6.7.1/userguide/compatibility.html) Adding in the kotlinOptions to address the following error: ``` Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6. Please specify proper '-jvm-target' option ``` And adding in related JVM configuration for consistency

view details

OdysseusLives

commit sha 0d34458e41982c74b5359c04e1890a05e5300c91

Merge pull request #207 from nebula-plugins/kotlin-1.4.10 Use Kotlin 1.4.10 and add explicit Java 1.8 configuration

view details

push time in 6 days

PR merged nebula-plugins/gradle-dependency-lock-plugin

Use Kotlin 1.4.10 and add explicit Java 1.8 configuration

Gradle 6.7.1 is tested through Kotlin 1.4.0 (https://docs.gradle.org/6.7.1/userguide/compatibility.html)

Adding in the kotlinOptions to address the following error:

Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6. Please specify proper '-jvm-target' option

And adding in related JVM configuration for consistency

+72 -33

1 comment

2 changed files

OdysseusLives

pr closed time in 6 days

delete branch nebula-plugins/gradle-resolution-rules-plugin

delete branch : kotlin-1.4.0

delete time in 6 days

push eventnebula-plugins/gradle-resolution-rules-plugin

Aubrey Chipman

commit sha 2df28f6a603339612076c58b6291398d3bef86f0

Use Kotlin 1.4.0 Gradle 6.7.1 is tested through Kotlin 1.4.0 (https://docs.gradle.org/6.7.1/userguide/compatibility.html) Adding in the kotlinOptions to address the following error: ``` Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6. Please specify proper '-jvm-target' option ```

view details

Aubrey Chipman

commit sha b62f94e8f4c4262a46365a0257022f33531c7d2d

Add explicit Java 1.8 configuration

view details

OdysseusLives

commit sha 8e6c38a476e05cfe101c26c828df77eebdad4cfa

Merge pull request #132 from nebula-plugins/kotlin-1.4.0 Use Kotlin 1.4.0

view details

push time in 6 days

PR merged nebula-plugins/gradle-resolution-rules-plugin

Reviewers
Use Kotlin 1.4.0

Gradle 6.7.1 is tested through Kotlin 1.4.0 (https://docs.gradle.org/6.7.1/userguide/compatibility.html)

Adding in the kotlinOptions to address the following error:

Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6. Please specify proper '-jvm-target' option
+55 -35

2 comments

7 changed files

OdysseusLives

pr closed time in 6 days

pull request commentnebula-plugins/gradle-dependency-lock-plugin

Use Kotlin 1.4.10 and add explicit Java 1.8 configuration

Coverage Status

Coverage remained the same at 74.93% when pulling 6712ac9688f8847799b46a57755fe861e5c88072 on kotlin-1.4.10 into 7987d353022b9509cdea66fe6feac63155d2dfec on master.

OdysseusLives

comment created time in 6 days

PR opened nebula-plugins/gradle-dependency-lock-plugin

Use Kotlin 1.4.10 and add explicit Java 1.8 configuration

Gradle 6.7.1 is tested through Kotlin 1.4.0 (https://docs.gradle.org/6.7.1/userguide/compatibility.html)

Adding in the kotlinOptions to address the following error:

Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6. Please specify proper '-jvm-target' option

And adding in related JVM configuration for consistency

+72 -33

0 comment

2 changed files

pr created time in 6 days

create barnchnebula-plugins/gradle-dependency-lock-plugin

branch : kotlin-1.4.10

created branch time in 6 days

pull request commentnebula-plugins/gradle-resolution-rules-plugin

Use Kotlin 1.4.0

That's a good plan! Thanks for the compatibility thoughts. I've updated this PR with additional explicit Java 1.8 configuration and will then upgrade to 1.4.10

OdysseusLives

comment created time in 7 days

push eventnebula-plugins/gradle-resolution-rules-plugin

Aubrey Chipman

commit sha b62f94e8f4c4262a46365a0257022f33531c7d2d

Add explicit Java 1.8 configuration

view details

push time in 7 days

PR opened nebula-plugins/gradle-resolution-rules-plugin

Reviewers
Use Kotlin 1.4.0

Gradle 6.7.1 is tested through Kotlin 1.4.0 (https://docs.gradle.org/6.7.1/userguide/compatibility.html)

Adding in the kotlinOptions to address the following error:

Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6. Please specify proper '-jvm-target' option
+43 -35

0 comment

7 changed files

pr created time in 7 days

create barnchnebula-plugins/gradle-resolution-rules-plugin

branch : kotlin-1.4.0

created branch time in 7 days

push eventnebula-plugins/gradle-lint-plugin

Aubrey Chipman

commit sha 6eda9cd91d36b9b65397d70433bcb268ae943af5

Introduce DeprecationLoggerUtils to assist with Gradle DeprecationLogger package change

view details

push time in 7 days

issue closednebula-plugins/gradle-ospackage-plugin

Disabling add parent directories option not working

The options addParentDirs = false as provided in the example:

from('endorsed') {
            // Will tell redline-rpm not to auto create directories, which
            // is sometimes necessary to avoid rpm directory conflicts
            addParentDirs = false
            into '/usr/share/tomcat/endorsed'
        }

does not seem to work.

Trying

from('scripts/anet.service') {
			addParentDirs = false
			into '/etc/systemd/system/'
		}
[root@test-ansible-redhat76-01 ~]# rpm -qlp /opt/ansible/anet/anet-2.1.33-133-g529c3de10-2.x86_64.rpm | grep systemd 

outputs:

/etc/systemd
/etc/systemd/system
/etc/systemd/system/anet.service

expected output:

/etc/systemd/system/anet.service

causing error:

Transaction check error:
  file /etc/systemd from install of anet-0:2.1.33~133~g529c3de10-2.x86_64 conflicts with file from package systemd-219-62.el7_6.16.x86_64
  file /etc/systemd/system from install of anet-0:2.1.33~133~g529c3de10-2.x86_64 conflicts with file from package systemd-219-62.el7_6.16.x86_64

Causing: NCI-Agency/anet#3303 Related: #120, #355, https://serverfault.com/questions/775647/installing-rpm-package-to-systemd/775653

closed time in 7 days

midmarch

issue commentnebula-plugins/gradle-ospackage-plugin

Disabling add parent directories option not working

The issue was that this

from('endorsed') {
            // Will tell redline-rpm not to auto create directories, which
            // is sometimes necessary to avoid rpm directory conflicts
            addParentDirs = false
            into '/usr/share/tomcat/endorsed'
        }

was not directly part of the distRpm task, but defined in a dependency.

After moving it to distRpm it worked.

midmarch

comment created time in 7 days

delete branch nebula-plugins/gradle-resolution-rules-plugin

delete branch : investigate-locking-interactions

delete time in 8 days

push eventnebula-plugins/gradle-resolution-rules-plugin

Aubrey Chipman

commit sha b3d2b0551bb04f8223cc611954e1823aed58c6b5

Cleanup some tests

view details

Aubrey Chipman

commit sha 1ada274f122b68c3069a2d4162d54df1fd14bde7

Add a test use-case where there are non-locked resolution rules and locked dependencies to see the errors due to locked state out of date. This is a rare use case, as resolution rules are typically distributed as a jar, but it can occur. In this case, core alignment takes precedence over the Nebula locking mechanism of useTarget/useVersion and the DependencyResolutionVerifier instead fails with an error that the Dependency lock state is out of date. This is introduced in the gradle-dependency-lock-plugin 11.1.+ This commit also updates the project to use gradle-dependency-lock-plugin 11.1.0-rc.1

view details

Aubrey Chipman

commit sha d78d9ff5d744ec90777dc8c7a4f7ec5e27afc8ba

Adding tests for alignment, locking, and downgrading dependencies

view details

OdysseusLives

commit sha ea49f285ef03ba07cda86aca5c8cf4924c80a37b

Merge pull request #131 from nebula-plugins/investigate-locking-interactions Investigate locking interactions

view details

push time in 8 days

PR merged nebula-plugins/gradle-resolution-rules-plugin

Reviewers
Investigate locking interactions

Adding tests with Nebula & core Gradle alignment related to updates to the locking plugin, so we can see the expected results

+723 -94

0 comment

8 changed files

OdysseusLives

pr closed time in 8 days

PR opened nebula-plugins/gradle-resolution-rules-plugin

Reviewers
Investigate locking interactions

Adding tests with Nebula & core Gradle alignment related to updates to the locking plugin, so we can see the expected results

+723 -94

0 comment

8 changed files

pr created time in 8 days

IssuesEvent

issue commentnebula-plugins/gradle-ospackage-plugin

Report bounced back to draft after submission

The options addParentDirs = false as provided in the example:

from('endorsed') {
            // Will tell redline-rpm not to auto create directories, which
            // is sometimes necessary to avoid rpm directory conflicts
            addParentDirs = false
            into '/usr/share/tomcat/endorsed'
        }

does not seem to work.

Trying

from('scripts/anet.service') {
			addParentDirs = false
			into '/etc/systemd/system/'
		}

still results in:

[root@test-ansible-redhat76-01 ~]# rpm -qlp /opt/ansible/anet/anet-2.1.33-133-g529c3de10-2.x86_64.rpm 
/etc/systemd
/etc/systemd/system
/etc/systemd/system/anet.service

causing error:

Transaction check error:
  file /etc/systemd from install of anet-0:2.1.33~133~g529c3de10-2.x86_64 conflicts with file from package systemd-219-62.el7_6.16.x86_64
  file /etc/systemd/system from install of anet-0:2.1.33~133~g529c3de10-2.x86_64 conflicts with file from package systemd-219-62.el7_6.16.x86_64

Causing: NCI-Agency/anet#3303 Related: #355, https://serverfault.com/questions/775647/installing-rpm-package-to-systemd/775653

midmarch

comment created time in 8 days

more