From fc4bb70dfb3bfffe2c72ae3d421226b8720b03f2 Mon Sep 17 00:00:00 2001 From: Tglman Date: Mon, 7 Oct 2024 14:39:25 +0100 Subject: [PATCH] chore: removed ci build not used anymore --- Jenkinsfile | 61 ----------------------------------------------------- README.md | 42 ++---------------------------------- 2 files changed, 2 insertions(+), 101 deletions(-) delete mode 100755 Jenkinsfile diff --git a/Jenkinsfile b/Jenkinsfile deleted file mode 100755 index 2f559d9..0000000 --- a/Jenkinsfile +++ /dev/null @@ -1,61 +0,0 @@ -@Library(['piper-lib', 'piper-lib-os']) _ - -properties([[$class: 'BuildDiscarderProperty', strategy: [$class: 'LogRotator', numToKeepStr: '4']]]); - -node { - - - stage('build') { - sh "rm -rf *" - sh "cp /var/jenkins_home/uploadedContent/settings.xml ." - - dockerExecute( - dockerImage:'ldellaquila/maven-gradle-node-zulu-openjdk8:1.1.0', - dockerWorkspace: '/orientdb-gremlin-${env.BRANCH_NAME}' - ) { - - try{ - sh "rm -rf orientdb" - sh "rm -rf orientdb-studio" - sh "rm -rf orientdb-gremlin" - - checkout( - [$class: 'GitSCM', branches: [[name: env.BRANCH_NAME]], - doGenerateSubmoduleConfigurations: false, - extensions: [], - submoduleCfg: [], - extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'orientdb']], - userRemoteConfigs: [[url: 'https://github.com/orientechnologies/orientdb']]]) - - checkout( - [$class: 'GitSCM', branches: [[name: env.BRANCH_NAME]], - doGenerateSubmoduleConfigurations: false, - extensions: [], - submoduleCfg: [], - extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'orientdb-studio']], - userRemoteConfigs: [[url: 'https://github.com/orientechnologies/orientdb-studio']]]) - - checkout( - [$class: 'GitSCM', branches: [[name: env.BRANCH_NAME]], - doGenerateSubmoduleConfigurations: false, - extensions: [], - submoduleCfg: [], - extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'orientdb-gremlin']], - userRemoteConfigs: [[url: 'https://github.com/orientechnologies/orientdb-gremlin']]]) - - - withMaven(mavenLocalRepo: '${HOME}/.m2/repository', globalMavenSettingsFilePath: 'settings.xml') { - sh "cd orientdb-studio && mvn clean install -DskipTests" - sh "cd orientdb && mvn clean install -DskipTests" - sh "cd orientdb-gremlin && mvn clean deploy" - } - }catch(e){ - slackSend(color: '#FF0000', channel: '#jenkins-failures', message: "FAILED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]' (${env.BUILD_URL})\n${e}") - throw e - } - slackSend(color: '#00FF00', channel: '#jenkins', message: "SUCCESS: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]' (${env.BUILD_URL})") - } - } - -} - diff --git a/README.md b/README.md index 8bce762..1f24570 100644 --- a/README.md +++ b/README.md @@ -1,42 +1,4 @@ -# orientdb-gremlin +## This branch is not in use anymore, the development moved to the gremlin folder of the main OrientDB repository [https://github.com/orientechnologies/orientdb/](https://github.com/orientechnologies/orientdb/) -[![REUSE status](https://api.reuse.software/badge/github.com/orientechnologies/orientdb-gremlin)](https://api.reuse.software/info/github.com/orientechnologies/orientdb-gremlin) +On this repo is only active the branch 3.2.x -[Apache TinkerPop](https://tinkerpop.apache.org/) 3 graph structure implementation for OrientDB. This started off as just a proof of concept, but thanks to a lot of help it's now in a really good shape and it has been officially adopted by the OrientDB team to be part of OrientDB `v3.x` and should eventually replace OrientDB's `graphdb` implementation that is still on TinkerPop 2. - -The main area that need some more work is index lookups - currently it does find the right index for a simple case, e.g. `g.V.hasLabel("myLabel").has("someKey", "someValue")`. However if there are multiple indexes on the same property, or if there the traversal should better use a composite index, that's not handled well yet. If you feel inclined you can add these cases to the `OrientGraphIndexTest.java`. The function that looks up indexes is `OrientGraphStep.findIndex`. - -## Tests -* you can run the standard tinkerpop test suite with `mvn install -P release` -* there are some additional tests that you can run independently with `mvn test` -* additionally there is a separate suite of tests in the `tests-scala` directory which you can run using `sbt test` -* to automatically format the code (travis CI enforces a format check), just run `mvn clean install` - -## Usage -Have a look at the tests-scala which demonstrates the usage. There's also an orientdb example project in [gremlin-scala-examples](https://github.com/mpollmeier/gremlin-scala-examples). - -## Labels and classes -Vertices and Edges are stored as classes based on their label. In order to allow vertices and edges to use the same label, the implementation prepends `V_` or `E_` in the class name: -* vertex with label `user` -> classname `V_user` -* edge with label `user` -> classname `E_user` - -## Migrations -You might want to use [orientdb-migrations](https://github.com/springnz/orientdb-migrations) to create a schema with indexes etc. - -## Release -* upgrade version: remove SNAPSHOT (driver/pom.xml and tests-scala/build.sbt) -* commit on branch, push, create PR on github -* await green light from travis -* merge PR on github -* then execute -``` -* mvn pull -* mvn clean deploy -Prelease -* git tag VERSION -``` -* bump versions to next SNAPSHOT (pom.xml, build.sbt) -* then -``` -* git push -* git push --tags -```