Picking the right architecture = Picking the right battles + Managing trade-offs
| org.carlspring.strongbox.providers.repository.MavenProxyRepositoryProviderTestIT#whenDownloadingArtifactMetadataFileShouldBeMergedWhenExist | |
| Stacktrace | |
| java.lang.NullPointerException | |
| at org.carlspring.strongbox.providers.repository.MavenProxyRepositoryProviderTestIT.whenDownloadingArtifactMetadataFileShouldBeMergedWhenExist(MavenProxyRepositoryProviderTestIT.java:109) | |
| Standard Output | |
| 01:13:10.177 03-02-2020 | DEBUG | kJoinPool-1-worker-2 | o.c.strongbox.services.ArtifactManagementService | Artifact checksum matchings: artifact-[strongbox:/storage0/rmmcjtit-snapshots/org/carlspring/strongbox/strongbox-metadata-one/2.0-SNAPSHOT/strongbox-metadata-one-2.0-20190512.202015-1-javadoc.jar]; ext-[md5]; matched-[[MD5]]; unmatched-[null]; checksum-[3397bc670f840b92ee0d7326ac0f4633] | |
| 01:13:10.177 03-02-2020 | DEBUG | kJoinPool-1-worker-2 | o.c.s.storage.checksum.ChecksumCacheManager | Removed [strongbox:/storage0/rmmcjtit-snapshots/org/carlspring/strongbox/strongbox-metadata-one/2.0-SNAPSHOT/strongbox-metadata |
| license: gpl-3.0 |
Influenced mostly by http://bl.ocks.org/mbostock/d1f7b58631e71fbf9c568345ee04a60e
| node { | |
| echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1' | |
| echo 'No quotes, pipeline command in single quotes' | |
| sh 'echo $BUILD_NUMBER' // 1 | |
| echo 'Double quotes are silently dropped' | |
| sh 'echo "$BUILD_NUMBER"' // 1 | |
| echo 'Even escaped with a single backslash they are dropped' | |
| sh 'echo \"$BUILD_NUMBER\"' // 1 | |
| echo 'Using two backslashes, the quotes are preserved' | |
| sh 'echo \\"$BUILD_NUMBER\\"' // "1" |
Create new filters and create new labels.
from:(notifications@github.com) AND {"Patch Links" "approved this pull request." "requested changes on this pull request." "commented on this pull request." "pushed 1 commit." "pushed 2 commits." "pushed 3 commits."}
label: gh-pull-request
Note: Nexus group repositories (good example in this StackOverflow question) are out of this tutorial's scope. In any case, deployment to group repositories is currently still an open issue for Nexus 3 (and not intended ever to be implemented in Nexus 2). Thus, it is assumed that we'll push & pull to/from the same repository, and ignore the idea of groups hereon in.
Ask your sysadmin for a username & password allowing you to log into your organistation's Nexus Repository Manager.
Test the login credentials on the Nexus Repository manager at: http://localhost:8081/nexus/#view-repositories (localhost in our case is replaced by a static IP, and can only be connected to over VPN). If your organisation requires a VPN to connect to it, connect to that VPN before proceeding with this tutori
| <html xmlns:o="urn:schemas-microsoft-com:office:office" | |
| xmlns:w="urn:schemas-microsoft-com:office:word" | |
| xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" | |
| xmlns="http://www.w3.org/TR/REC-html40"> | |
| <head> | |
| <meta name=Title content=""> | |
| <meta name=Keywords content=""> | |
| <meta http-equiv=Content-Type content="text/html; charset=utf-8"> | |
| <meta name=ProgId content=Word.Document> |
| #!/bin/bash | |
| # input folders: | |
| # version : contains a file called number with the current version | |
| # source-code : contains the source code | |
| # output folders: | |
| # build: contains the built jar | |
| set -ex |