I'm wondering how to deploy artifacts to Artifactory's Distribution repo .
Pushing directly to the distribution repo from gradle (using the gradle-maven plugin) results in the following error:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':artifactoryDeploy'.
> java.io.IOException: Failed to deploy file. Status code: 404 Response message: Artifactory returned the following errors:
Could not find a local repository named my-distribution-repo to deploy to. Status code: 404
Seems I can't push to a repo that's not a local repo. Any ideas?
You can push to a local repository and then distribute the build to a distribution repository.
For example, with the JFrog CLI you can distribute in 3-4 steps:
Building a Gradle project.
Publishing the build information.
Promoting the build (Optional).
Distributing the build.
Related
I am working on Kibana version 7.16.2. I wanted to build Kibana distributable so I executed yarn build --skip-os-packages . But it failed with exist code with following error. Can anyone help me resolve this error?
Build error image ss
Also I wanted to know that whether the build folders that are required are completed because before error message I can see an info log saying "All bazel production build are completed".
I am trying to setup JFrog Pipelines. I am new to this so starting small with a pipleline that just has a single npm build step. The source code is taken from github. When I run the pipeline, I get a 404 not found error in the artifactory_configure task. I double checked the Artifactory Integration but the error persists. Any ideas on how to solve it.
Please make sure that you include the Artifactory context as part of the URL when creating the Artifactory integration. For example:
https://xxx.jfrog.io/artifactory
I have created proxy repos in Nexus 3 pointing to Nexus 2 hosted repositories. This is to snapshot and release repositories on Nexus 2. Now, on distributionManagement tag, I am using the proxy URLs and trying do a mvn clean deploy. I am getting the following error:
[INFO] Error deploying artifact: Failed to transfer file: http://nexus3url/repository/m2-snapshots/path/abc-1.1.4-SNAPSHOT.pom. Return code is: 405
Has anyone tried this?
As indicated in the comments, you can only deploy to Maven Hosted Repositories, not Proxies. This is by design.
I faced same issue when I try to deploy application into nexus 3 repository.
In my case the url is not proxy but path was wrong.
If you are trying to deploy snapshot version make sure url pointing to nexus snapshot repository location.
if it is release version url should point to release repository.
Your Nexus folder type should be host and try
mvn deploy
command by using pipeline.
configFileProvider([configFile(fileId: '1880060f-32be-4888-a77d-eb046cab6981', variable: 'MAVEN_SETTINGS')]) {
sh "/jenkins_new/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.5.0/bin/mvn -s $MAVEN_SETTINGS deploy:deploy-file -DgroupId=net.cyc -DartifactId=${pom.artifactId} -Dversion=${pom.version} -DgeneratePom=true -Dpackaging=jar -DrepositoryId=nbtnexus -Durl=https://dexus.connectcare.net/repository/maven-snapshots/ -DpomFile=pom.xml -Dfile=target/${pom.artifactId}-${pom.version}.${pom.packaging}"
}
I've created package and published it, It is just a simple wrapper of "phantom"
I deployed it using
sudo meteor publih --create
then added it to my app
$> meteor show sasi513:phantom#1.0.0
Version 1.0.0 : phantom node Package wrapper
Architectures: os.linux.x86_32+web.browser+web.cordova
Maintained by sasi513.
EDIT
Then when I try to deploy it meteor deploy xxx.meteor.com
Errors prevented deploying:
While building the application:
error: Unable to download package builds for this architecture.
and I tried to publish-for-arch
sudo meteor publish-for-arch sasi513:phantom#1.0.0
sasi513:phantom: updating npm dependencies -- phantom...
Bundling build...
Creating package build...
Uploading build...
Publishing package build...
Error from package server
: Cannot override existing build [403]
What is wrong here?Anyone has idea about this
The documentation says:
You need to run publish-for-arch from a different architecture to
upload a different build.
Are you running the command on a different architecture? Or the same machine? Because running the command on the same machine wont work.[1] Based on your description, it sounds like you didn't try it from the other architecture you want to support.
[1] http://docs.meteor.com/#meteorpublishforarch
Is there some kind of sbt plugin that enables publishing result to repository (i.e nexus).
I heard about sbt-native-packager but I need to create tarball (*.tar) and publish it to repository. I prepeare my own task that depends on dist and it repackages result from zip to tar. Next I just try to modify it with description available here: https://groups.google.com/forum/#!topic/play-framework/Td389FbdgCY. Unfortunately I get:
[error] java.lang.AssertionError: assertion failed: Internal task engine error: nothing running. This usually indicates a cycle in tasks.
[error] Calling tasks (internal task engine state):
[error] Task((taskDefinitionKey: ScopedKey(Scope(Select(ProjectRef(file:/C:/src/cms/,cms)),Global,Global,Global),projectDependencyArtifacts))) -> Calling
What is more additionaly to publishing package in repository I need to automatically create create tag for release in mercurial.